Any luck tracking this down? Are you using the PBS runner or a DRMAA one (and if DRMAA what DRM)?

Are you using the local job runner for anything? If yes - it may be worth splitting the local job handling into its own handler to eliminate that as the source of the problem.

Are you using Postgres - and if yes have you enabled the option database_engine_option_server_side_cursors = True?

If you have some time, a test setup and can reproduce - it may be worth running with use_memdump = True in galaxy.ini - I am forget what it does exactly but I feel like I have used it to track down memory problems in the past....

Long story short - I have no clue none of the changes we made that release come to mind as possible culprits - very sorry.

-John

On Mon, Dec 1, 2014 at 8:43 AM, Langhorst, Brad <Langhorst@neb.com> wrote:

I’m running

hg id

2092948937ac+ (stable) release_2014.10.06

After a few days my web runners start to use excessive memory…

This was not the case in previous releases.

I did upgrade a few toolshed items around the same time and tried to add some reference genomes via the data manager tools.

Anybody else seeing this problem?

Any hints on the best way to track this down?

I do not relish a daily restart to paper over this issue…

(htop screenshot attached)

Brad

--

Bradley W. Langhorst, Ph.D.

Applications and Product Development Scientist

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/