Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-14 Thread Nate Coraor
On Feb 13, 2013, at 5:56 PM, Anthonius deBoer wrote: Interesting! But maybe it is not the manager that is the bottleneck, but which process is the one that takes the inputs from the webpage (or in the API) and prepares all the files that are produced by the workflows? I guess it is the

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-14 Thread James Taylor
On Thu, Feb 14, 2013 at 10:40 AM, Nate Coraor n...@bx.psu.edu wrote: What I am facing, is that I have 100 FASTQ pairs or so, for a single flowcell, I can start the analysis of that set from the UI, but it will just crank through them and takes about 2-4 minutues for each pair to be

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-13 Thread Nate Coraor
On Feb 7, 2013, at 2:43 PM, Anthonius deBoer wrote: That's very unfortunate... I have a ton of tools and I guess now I have to create a package for them in a local toolshed to update them in a running galaxy server? In any case...The toolshed installation also does not work for me...I

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-13 Thread Anthonius deBoer
Would this problem go away if I only used ONE webserver in my proxy setting and not use a balancer?I may not need it and if it means I could not use the toolshed effectively, it may be worth it not to use balancing..What i really need is the manager being balanced, since submitting a workflow with

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-13 Thread Nate Coraor
On Feb 13, 2013, at 4:12 PM, Anthonius deBoer wrote: Would this problem go away if I only used ONE webserver in my proxy setting and not use a balancer? I may not need it and if it means I could not use the toolshed effectively, it may be worth it not to use balancing.. No, because your

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-13 Thread Anthonius deBoer
Interesting!But maybe it is not the manager that is the bottleneck, but which process is the one that takes the inputs from the webpage (or in the API) and prepares all the files that are produced by the workflows?I guess it is the MAIN server?THAT is the one that is the bottleneck I think

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-07 Thread Dannon Baker
Unfortunately not, and with the migration of tools to the toolshed installation mechanism I don't imagine this will be addressed (at least by the team) anytime soon. If you wanted you could probably write a script that would reload a specified tool in each of the separate web processes, or

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-07 Thread Anthonius deBoer
That's very unfortunate...I have a ton of tools and I guess now I have to create a package for them in a local toolshed to update them in a running galaxy server?In any case...The toolshed installation also does not work for me...I still have to restart galaxy, even after using the toolshed

Re: [galaxy-dev] Reloading a tools configuration does not seem to actually work

2013-02-06 Thread Anthonius deBoer
I am indeed using multiple web processes and I guess I am talking about the "old" admine tool reloader...Is there any other way to do this for your own tools that you just manually place in tools etc.?ThonOn Feb 05, 2013, at 06:22 PM, Dannon Baker dannonba...@me.com wrote:Are you using multiple