I have recently cloned a Deski job server in order to try and get more reports scheduled in a certain timeframe. The existing server had a Maximum Concurrent Jobs of 5 (which I have left) and I have changed the cloned server just to run 1 report at a time to see if the 6 (in total) would be faster than the 5. (This had been recommended rather than upping the max concurrent jobs on existing job server)
Currently it isn’t any faster to get through all the reports as despite 6 being able to run at one, the performance has suffered quite a lot. As a result, I was wondering if there’s an optimum set up when having more than 1 job server running, or if it is totally reliant on something else. If the latter, are there step I can take to improve overall performance?
Any comments or suggestions would be much appreciated.
Regards
When you run the jobs concurrently , performance depends on other factors too. RAM size of your BO server should be capable of handling all jobs concurrently otherwise they might even fail with error not able to process at job server.
When you concurrently run all jobs , go to task manager of BO server and see performance.If your memory size is maxed then its performance would be very bad.
You need to ensure you have enough RAM size to run.As far as i know least requirment for BO server is 4 GB RAM because it takes around 3 GB to run all BO services and 1 GB left for other work.
In my case, i set the parameter to 50 and hit on 50 jobs to run concurrently but server went down.then i had seen memory size,it was maxed.then i again changed the parameter to 20,then it is working okay. however even your max parameter is set to 20 at a time and you are hitting 50 reports in one-go then also server will go down since your RAM has to be in proportion to what all the things you are running.Well as a whole it is all about RAM,that you have to see.
(BOB member since 2009-09-03)
(BOB member since 2009-08-11)
(BOB member since 2008-10-28)