CPU Cores utilization

saggitarianamit

<p>I have a production system - Actuate iServer 11SP4</p>
<p> </p>
<p>We have three kinds of reports - Spreadsheets, e.Reports and IOBs</p>
<p> </p>
<p>License is for 3 CPU Cores and PMD is bound to CPU core 0,1,2 . I have few questions</p>
<p> </p>
<p>1) jsrvr11 is for running transient jobs and viewing reports. Does this means everytime I schedule a report or run it on demand a jsrvr11 will be spawned ? Becuase both types would require viewing of reports.</p>
<p>2) If I run three transient reports does that means three jsrvr11 process would be spwaned ?  and how many CPU cores would be used?</p>
<p> </p>
<p>3) If I schedule 3 reports (all eSpreadsheet reports) does that mean three jfctsrvr11 process would be spwaned?</p>
<p>4) Are jsrvr11 and jfctsrvr11 bound to CPUs? Meaning can one report run only on one CPU core at a time?</p>
<p> </p>
<p>Any insight would be highly appreciated</p>
<p> </p>
<p>Regards,</p>
<p>Amit</p>
<p> </p>
<p> </p>

RSiegler

<div>saggitarianamit,</div>
<div> </div>
<div>1) No, a single jsrvr11 process can be used for several concurrent reports for synchronous running/viewing with a few caveats:</div>
<div>     a) The reports will be of the same type (Dashboard is different than BIRT Report is different than e.SpreadSheet report, etc)</div>
<div>     b ) e.Reports will not use any of the jsrvr or jfctsrvr factories, and instead use fctsrvr and viewsrv</div>
<div>     c) IOBs will use the integration server and an appropriate factory of report if used as a data source</div>
<div> </div>
<div>2) No. This is all configurable with minimum and maximum factories, and CPU core usage would typically be limited to one, however this can vary based on different circumstances.</div>
<div> </div>
<div>3) Potentially. Each jfctsrvr process handles a single report at a time asynchronously. Depending on the configuration this could potentially start 3 factories, however that is configurable with minimum and maximum factories.</div>
<div> </div>
<div>4) They are not specifically bound to a single CPU, but rather will be bound to CPUs that the application is bound to.</div>