On Sep 15, 2012, at 11:05 PM, Jeremy Goecks <jeremy.goe...@emory.edu> wrote:
>> is there a way to determine whether Trackster is the cause?
> The only place where Trackster caches data is in the SummaryTreeDataProvider.
> In galaxy-central, the relevant line is 709 in
> lib/galaxy/visualization/genome/data_providers.py :
> CACHE = LRUCache( 20 ) # Store 20 recently accessed indices for performance
> Try setting the cache size low or to 0 and see if that addresses the memory
I'll try this in combination with a bump in mem allocated to the VM, should
take care of it. Thanks!
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: