Re: [galaxy-dev] database engine pool size

2012-04-18 Thread Dannon Baker 
On Mar 26, 2012, at 12:18 PM, Shantanu Pavgi wrote:
 {{{
 TimeoutError: QueuePool limit of size 40 overflow 50 reached, connection 
 timed out, timeout 30
 }}}
 
 These limits are not reached for regular (non-workflow) galaxy jobs. Any help 
 on optimum values for these settings or performance tuning for workflow runs 
 would be appreciated. 

Hi Shantanu,

Two things could help here:

1. Enable database_engine_option_strategy = threadlocal in your 
universe_wsgi.ini
2. Run additional Galaxy processes: 
http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Web%20Application%20Scaling

-Dannon
___
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:

  http://lists.bx.psu.edu/

[galaxy-dev] database engine pool size

2012-03-26 Thread Shantanu Pavgi 

I would like to get some idea about 'database_engine_option_pool_size' and 
'database_engine_option_max_overflow'  settings. We seem to hit both of these 
limits whenever a user runs a large workflow with following error: 

{{{
TimeoutError: QueuePool limit of size 40 overflow 50 reached, connection timed 
out, timeout 30
}}}

These limits are not reached for regular (non-workflow) galaxy jobs. Any help 
on optimum values for these settings or performance tuning for workflow runs 
would be appreciated. 

Version Info: CentOS 5.7, PostgreSQL 8.4.9, Python 2.6.6, Galaxy revision 
26920e20157f. 

--
Thanks,
Shantanu
___
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:

  http://lists.bx.psu.edu/