I am relatively new to galaxy so if you get a different response from one of the core team ignore this.
One thing I would check is the underlying database.
What do you have set for "database_connection" in your galaxy.ini file.
Especially if you are using the default sqlite this could be the issue. As that is store in a single file on disk.
Whichever database you have make sure it has enough resources to handle what will now be a large size.
From: galaxy-dev [email@example.com] on behalf of Poole, Richard [firstname.lastname@example.org]
Sent: Wednesday, July 08, 2015 9:04 PM
Subject: [galaxy-dev] Slow repsonses viewing histories
I am having trouble right now with my own personal account on my production server. Grid refreshes are taking a huge amount of time (e.g. when viewing ‘saved histories’ or even generating the dataset list for a single history). My account is very
full of data (1TB), could it be this?
There are no obvious messages in the logs though so I am a bit stumped as to why.I do not have the same trouble when impersonating other users with fairly full accounts. Perhaps a database issue (I do not know how to ‘cleanup’ the database or
indeed Galaxy user accounts). Any thoughts?
Richard J Poole PhD
Wellcome Trust Fellow
Department of Cell and Developmental Biology
University College London
21 University Street, London WC1E 6DE
Office (518 Rockefeller): +44 20 7679 6577 (int. 46577)
Lab (529 Rockefeller): +44 20 7679 6133 (int. 46133)