How many reports are recommended to run on each crystal reports job server in 3.1?
ie: I have one crystal reports job server defined right now with 35 as the number of reports it can run. Is there a recommended setting?
unds 
(BOB member since 2006-12-09)
Depends very much on the complexity of the reports, the average time it takes for a report to run, the hardware resources available and the network infrastructure. Unlimited is the default setting (I believe) but as you’ve noticed, you can change that.
The sizing guide (ask your SAP rep) may help you out here.
Orange 
(BOB member since 2006-09-18)
I was informed by SAP that there is no sizing guide for 3.1 that is made public, they have a document that they refer to internally only.
They mentioned that 5 jobs per job server was the recommended setting.
So, if I wanted 30 concurrent reports to run, I would create 6 crystal reports job servers. Does this seem right?
unds (BOB member since 2006-12-09)
Well, there is definitely a sizing guide out there for XI 3.0 (do a search here on the forum and you’ll find several posters that have received it from SAP, so it is NOT just an internal doc - you can tell them that 
).
I did miss the fact you were talking about the job server - sorry. The default setting is 5 - it cannot really be a recommended number (shoot that rep) as it depends on the things I mentioned earlier.
Anyway - back to the sizing guide. As you are only looking for a Crystal Job server, you can get away with having a look at the XIr2 sizing guide as nothing has really changed for the Crystal reports. The sizing guide can be found here (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f01d32ea-8164-2b10-f690-9db86769cfe8).
Other than that, I would personally recommend creating several job servers if you need to run more jobs at the same time. Have them all running with the default setting of 5 and monitor from there. Use auditing to figure out how busy your jobservers are.
Good luck!
Orange (BOB member since 2006-09-18)
The default for the Crystal Reports Job Server is typically 5 jobs per cpu. It used to be that the thresholds for the Crystal Reports Job Server were:
1 CPU handles 5 concurrent jobs.
1 service can handle 20 concurrent jobs.
With multi-core processors and reports of varying complexity you can probably guess that this is not a firm rule. Do the math and then experiment if possible. VMware comes in handy as far as allocating different numbers of virtual cpu’s. If you have cpu licensing you may be in a bit of a bind though as far as allocating additional cpu.
clarence (BOB member since 2005-11-18)
we have 2 CPU’s and we are using a VM server.
I was planning on setting up 4 crystal reports job servers, each limiting 5 reports on each job server.
So based on the sizing guide, as we only have 2 CPU’s, we should have a limit of 10 reports running?
unds (BOB member since 2006-12-09)
Sounds like you might want to start with a single Crystal Reports Job Server configured to allow a MAX of 10 concurrent jobs. In fact, if you plan to have other jobs running on the server (webi?) you will probably want to stick with the default 5 jobs. What this means is that the Crystal Reports Job server will allow up to 5 Crystal Reports to be scheduled at the same time. Additional scheduled jobs will go into a queue until a prior job has completed. Do you have cpu licensing? Can you give the server more cpu’s?
clarence (BOB member since 2005-11-18)