This is a “Best Practice” question for BOE-XI (3.x).
I have dug through the 3.1 DEPLOYMENT training, Admin and Pattern documents, but none of them clearly discuss anything around installing multiple copies of the SAME service (eg. CMS, ReportJob) on the same physical server if it has more that 1 CPU.
The documents detail the “per CPU” limits of a service, but don’t detail if we should install multiple services to take advantage of the multiple CPUs available on a specific Physical Server.
For example - the Crystal Report Job Server can support five (5) simultaneous report jobs per CPU by default.
If we have a 2 CPU machine, do we run one (1) CRJS service - but increase the “Maximum Jobs Allowed” setting to Ten (10), or do we install two (2) CRJS services each with a default limit of Five (5)…?
Does this rule apply to all services including the One (1) CPU for One-Hundred (100) simultaneous requests sizing-limit on the CMS…?
Can you run more than one CMS service on a specific Physical Server…?
Absolutely you can run multiple services of the same type on the same box (i.e. vertical scaling). I seem to recall an old sizing guide for XI R2 that outlined pretty specific thresholds for vertical and horizontal scaling of services - I don’t know if this is now available for R3 as well…
Multiple CMSs (@cluster) is also possible on the same physical machine, but I suppose deploying both on the same machine eliminates what you could potentially gain in fault tolerance and distribution of processing load.
I will dig around a bit but I think a search on vertical scaling should provide some good information.
I see in the sizing notes that “Multiple Crystal Reports Processing(page) sever should not be installed on a single sever…”, so I was wondering if there were any other services that rule would apply to.
With the Crystal Report Job Servers we seem to be OK to increase the Max Jobs from the deafult of 5 to 10 for Dual-CPU or 20 for Qaud-CPU. I can see the running jobs in the METRICs screen increase.
However, the single CMS service does not have a CMC setting to manage “100 simultaneous requests” per CPU limit - so does the CMS auto-scale to handle 200 simultaneous requests on a Dual-CPU, etc…?
I think it does not, so installing additional CMS services is the only way to increase your “simultaneous requests” limits.
We have had “simultaneous requests” issues in the past when large volumes of reports are SCHEDULED for a single SPECIFIC point-in-time (eg. 1,000 pending instances waiting for 2 AM).
One service may requier to be to only one on a server(OS), other can use only one cpu and there are services that just don’t care about the number of cpu’s or other simular services that are installed on the same server(OS).
(BOB member since 2007-03-23)
(BOB member since 2006-08-30)
(BOB member since 2006-12-19)