ction_proxy'
>>> database_query_profiling_proxy = False
>>>
>>> # -- Files and directories
>>>
>>> Let me know if you think these settings are appropriate or need further
>>> tweaks.
>>>
>>> Thanks again for your responses so far,
>
__
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.org>]
on behalf of Poole, Richard [r.po...@ucl.ac.uk<mailto:r.po...@ucl.ac.uk>]
Sent: Wednesday, July 08, 2015 9:04 PM
To:
galaxy-dev@lists.galaxyproject.o
Yay, thank you so much Dannon! That was the jackpot! My user was also quite
happy.
Remind me to buy you a beer at the next GCC ;)
Cheers
Christian
On 24/07/15 17:50, Dannon Baker wrote:
Hey Christian,
I used /scripts/db_shell.py and something like
https://gist.github.com/dannon/e71b7aa9546fce
Hey Christian,
I used /scripts/db_shell.py and something like
https://gist.github.com/dannon/e71b7aa9546fcecf6e9e to reset problematic
BAM metadata. Basically, it selects all the large metadata and completely
strips out the new overly large optional attributes, leaving required
attributes alone.
Hi Nate, all
I would like to add my own version of the problem to this.
I, or rather my (inherited) Galaxy instance (which should be running 15.05+,
how do I find out?), have/s similar symptoms as Richard's did. In my case it
only occurs to a single user and we are not able to execute the "Save
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.
Christian
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.o
make sure it has enough resources to handle what
will now be a large size.
Christian
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.org>]
on behalf of Poole, Richard [r.po...@ucl.ac.uk<mailto:r.po...@ucl.a
Whichever database you have make sure it has enough resources to handle what
will now be a large size.
Christian
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.org>]
on behalf of Poole, Richard [r.po.
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.org>]
on behalf of Poole, Richard [r.po...@ucl.ac.uk<mailto:r.po...@ucl.ac.uk>]
Sent: Wednesday, July 08, 2015 9:04 PM
To:
galaxy-dev@lists.ga
le_name. I've noticed that retrieving this attribute
>> from the file system can be slow.
>>
>> Christian also provides good advice.
>>
>> On Thu, Jul 9, 2015 at 4:12 AM, Christian Brenninkmeijer <
>> christian.brenninkmei...@manchester.ac.uk> wrote
what
will now be a large size.
Christian
From: galaxy-dev
[galaxy-dev-boun...@lists.galaxyproject.org<mailto:galaxy-dev-boun...@lists.galaxyproject.org>]
on behalf of Poole, Richard [r.po...@ucl.ac.uk<mailto:r.po...@ucl.ac.uk>]
Sent: Wednesday, July 08,
ave 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
Wednesday, July 08, 2015 9:04 PM
To:
galaxy-dev@lists.galaxyproject.org<mailto:galaxy-dev@lists.galaxyproject.org>
Subject: [galaxy-dev] Slow repsonses viewing histories
Hi all,
I am having trouble right now with my own personal account on my production
server. Grid refreshes are taking a huge amount of tim
ists.galaxyproject.org] on behalf
> of Poole, Richard [r.po...@ucl.ac.uk]
> *Sent:* Wednesday, July 08, 2015 9:04 PM
> *To:* galaxy-dev@lists.galaxyproject.org
> *Subject:* [galaxy-dev] Slow repsonses viewing histories
>
> Hi all,
>
> I am having trouble right now with my own
of
Poole, Richard [r.po...@ucl.ac.uk]
Sent: Wednesday, July 08, 2015 9:04 PM
To: galaxy-dev@lists.galaxyproject.org
Subject: [galaxy-dev] Slow repsonses viewing histories
Hi all,
I am having trouble right now with my own personal account on my production
server. Grid refreshes are taking a huge amou
Hi all,
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?
T
16 matches
Mail list logo
