I'm using galxy-dist. That's why I don't have the setting. Thanks for
the information, I'll wait for the next stable release and update the
settings then.
Geert
On 03/26/2014 01:59 PM, Greg Von Kuster wrote:
The changeset that made this a configurable setting was committed to
the stable
hi Greg,
I don't have that setting in my universe. Should I just add it? The
output of hg summary is (hg incoming doesn't show any available updates):
parent: 12276:dc067a95261d tip
Added tag release_2014.02.10 for changeset 5e605ed6069f
branch: stable
commit: 22 modified, 1 deleted, 127
Hi Geert,
The setting should be in your universe_wsgi.ini.sample, and you woud have to
manually edit your universe_wsgi.ini to add it. I would say that 125 installed
packages is probably what is causing the slow starts. This feature is not
currently useful, so it can be set to not function
Hi Greg,
The setting was not in my universe_sample file. I added it, set log_info
to DEBUG and restarted galaxy.
The startup time remained the same, and there were many entries in the
log file indicating that the lag is indeed the creation of the
dependency system:
The changeset that made this a configurable setting was committed to the stable
branch in d270d3c, which was committed on 2014-02-19
https://bitbucket.org/galaxy/galaxy-central/commits/d270d3cf7627a42b6fac2aa69701deadb89c8ffc
If you are tracking the stable branch in the galaxy central repo
Dear all,
I'm wondering if the following behaviour is normal. Since I reinstalled
the latest galaxy distribution, every restart hangs/loads for up to 10
minutes at the following lines:
galaxy.model.migrate.check INFO 2014-03-25 15:56:57,965 At database
version 118
Hello Geert,
Do you have a lot of repositories installed from the Tool Shed into you Galaxy
instance? if so, the time you're experience may be due to loading the
in-memory installed repository registry. Using this registry is optional, but
the default configuration setting is to use it. You
