Question: Web Galaxy Server And Load
gravatar for Ann Holtz-Morris, M.S.
5.3 years ago by
Ann Holtz-Morris, M.S.80 wrote:
HI, Does anyone know how to check whether the Galaxy server(s) load is really high? My alignments, only 200,000 paired end reads seemed to be taking a long time. I read through the archives, and the answers were that 1) alignments take a while and that the server load really affects the turnaround time, and 2) But then again, it could also be your data & settings. I could not find how users could check whether the server load is really heavy, especially for alignments. I also suspect it could have been be my query being incorrectly set up because when the alignment finally did come back, the ~1% control DNA did not align correctly. Thanks aholtzmorris CONFIDENTIALITY NOTICE: This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message. Thank you.
galaxy • 701 views
ADD COMMENTlink modified 5.3 years ago by Jennifer Hillman Jackson25k • written 5.3 years ago by Ann Holtz-Morris, M.S.80
gravatar for Jennifer Hillman Jackson
5.3 years ago by
United States
Jennifer Hillman Jackson25k wrote:
Hi Ann, How long a job is in the waiting state "grey" will let you know how busy the queue (server/cluster) is. How long it is in the executing state "yellow" will let you know how long it takes to process. These are independent. That said, a ~1% control alignment failure may be reasonable - it just depends on the quality of your data, how strict the mapping parameters are, and how finished the reference genome is. Taking a look at some of the failures might help explain. Maybe run FastQC. Or a tool like Lastz can place a sequence quickly on the genome with control over things like coverage, identity, etc. Then, tool options can be turned, if you think this is the run-time issue. Keep in mind that making a run less sensitive will speed up processing, but also likely reduce the number of "hits". Help for each tool's form (and link to primary documentation) and testing is the best way to determine the optimal settings per experiment. The defaults are most often those recommended by the tool authors and not optimal for every query/genome. Hopefully this helps, Jen Galaxy team -- Jennifer Hillman-Jackson Galaxy Support and Training
ADD COMMENTlink written 5.3 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 121 users visited in the last hour