Just a quick question. The Crystal Elite Support was very vague when responding to this question. We are running 4 separate JobServers on each JSPS server. Each JobServer is set to run 5 threads at one time, giving a total of 20 maximum process threads that can run concurrently. When loading up the server with 100+ users, we see the jobs in the queue but can only see 5 to 7 threads (JobServerChild) / processes running or processing. Elite Support says that it will never show all twenty but that we should see something in the high teens. Any thoughts?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Jobserverchild and Concurrent Processes
- Thread starter nbk13nw
- Start date
I just want to clarify your setup:
You're running a quad-processor server as the JSPS and you've installed and enabled four job server services, each with the ability to handle up to 5 jobs, allowing for a total of 20 jobs on the server. Is this right?
What is the real issue? That your scheduled jobs are aren't being run, they're bogged down? Or is the issue that you just can't see how the job servers are performing? When you're viewing the metrics how do you know the the number of reports that are current running/pending/waiting are even scheduled reports (the only reports the Job Server handles)? Could they be on-demand reports, which use the Page Servers/Cache Servers?
Have you performed tests where you schedule a large number of jobs to run at the same exact time? Example: schedule a test report (or multiple reports) to run at least 60 times all at the exact same time (arbitrarily chosen) and check the metrics in Manage Settings to see how many jobs actually process at the same time.
You're running a quad-processor server as the JSPS and you've installed and enabled four job server services, each with the ability to handle up to 5 jobs, allowing for a total of 20 jobs on the server. Is this right?
What is the real issue? That your scheduled jobs are aren't being run, they're bogged down? Or is the issue that you just can't see how the job servers are performing? When you're viewing the metrics how do you know the the number of reports that are current running/pending/waiting are even scheduled reports (the only reports the Job Server handles)? Could they be on-demand reports, which use the Page Servers/Cache Servers?
Have you performed tests where you schedule a large number of jobs to run at the same exact time? Example: schedule a test report (or multiple reports) to run at least 60 times all at the exact same time (arbitrarily chosen) and check the metrics in Manage Settings to see how many jobs actually process at the same time.
- Thread starter
- #3
Yes, the setup you stated is correct. I thought that maybe the scheduled proceses were completing to fast for me to see them in the metrics tab. So, we loaded the system with 200 scheduled reports, it was then that I was able to see that all of the expected Child processes were indeed running as expected. Thanks for the reply!
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question