Assaf Gordon wrote:
My job-runner process is at 6% when no jobs are running, and between 30%-60% when there are running jobs - but that doesn't affect the web responsiveness any more - which is exactly what I was looking for. I'm just wondering if your runner is also at high CPU usage when there are running jobs, or is it a problem in my postgresql database configuration, or maybe it's something related to the local-runner (and doesn't affect servers which use SGE/PBS).
It does go up if the runner is tracking a lot of jobs, although I would expect that to be less with the local runner. The heartbeat log may tell you more about where those cycles are going.
My small contribution will be to add a wiki page: http://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling
And as always, I have another question: How does reloading a tool works when I have multiple processes running ? Only a single process will handle the HTTP request, so do they somehow communicate ?
Unfortunately, reloading a tool will only reload it in the app that the proxy happens to give you for that request. To reload the tool across the entire set of servers, you have to go to each proxied application and reload it. --nate