You can certainly adjust the two values as needed for your particular
environment. Also check in your universe_wsgi.ini for:
set_metadata_externally = True
Something else you might want to consider, and what we do to handle the load on
the server at http://usegalaxy.org, is starting more instances to balance the
load. For reference, our settings for pool_size and max_overflow are 10 and
for a good reference with more details on setting up a high performance galaxy
server in a production environment suitable for multiple users.
On Apr 21, 2011, at 1:47 PM, Liisa Koski wrote:
> We are running many NGS workflows at the same time on our local instance of
> Galaxy. They are crashing with the following error
> Error - <class 'sqlalchemy.exc.TimeoutError'>: QueuePool limit of size 5
> overflow 10 reached, connection timed out, timeout 30
> In the universe_wsgi.ini we made the following adjustments:
> # If the server logs errors about not having enough database pool
> # you will want to increase these values, or consider running more Galaxy
> # processes.
> database_engine_option_pool_size = 50 # this used to be 5
> database_engine_option_max_overflow = 100 # this used to be 100
> Those numbers were pulled out of a hat so I wanted to make sure what we were
> doing was correct. Is there a limit on the values? It doesn't appear to be
> crashing anymore but I still want to make sure.
> 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:
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: