4.3 years ago by
Certain tools now have an option included to report the mapping time (example: Bowtie2 (correction from Tophat2 - that will be coming soon!)). This is found in the full parameter settings, near the end. Please keep in mind that this does not include queue time. The public server is often busy - but how busy is the important bit.
Execute the job and see, it will vary, expectedly. Then permit the job to run to completion without stopping/restarting, or you will lose your original place in the queue, extending wait time.
Queue time is dependent on these major factors: the type of job you run (compute intensive jobs, often found in tool groups staring with an "NGS", go to our busiest queue - due to the jobs often executing for the longest time period), how many other users are also using the public Main instance (http://usegalaxy.org) or other Galaxy - if not using a local/dloud, and how many jobs are queued to execute prior to this one in any of your histories (prioritize if work is urgent). This wait time is difficult to predict, of course, but our team (and extended team) has been discussing methods, and our new configuration at TACC this past year offers more potential.
This all said, Main can very often be quite speedy. When you happen across such a window, it is a very good time to launch a workflow.
Hopefully this helps you both, Jen, Galaxy team
I wanted to know the run time for some jobs too, but as far as I've been able to figure out, there is no way to tell how long a job ran from the user end of things on galaxy (if anyone else has found otherwise, please correct me!).