Howdy, Andrew, One possibility is that there are more jobs on the cluster. I'm not familiar enough with the galaxy interface to know if there's an easy way to tell how much time the job sits on the cluster's queue waiting and how much time the job is actually running. Assuming there's no cluster difference, are the data conditions similar between what you are mapping now vs two weeks ago? I.e. number and length of reads, size of reference sequence, divergence, repeat content? Bob H On Dec 14, 2011, at 10:10 AM, Andrew South wrote:
Hi - is there a reason Lastz is very slow right now? I am mapping 2-3,000, reads against a single, 11Kb, sequence and find that jobs are either returning an error or taking 16-24hrs to get done. This time frame was more like 30 minutes two weeks ago. Is there a way to speed this up? Thanks in advance for any help. Andy
************************************************************ Please consider the environment. Do you really need to print this email?
The University of Dundee is a registered Scottish charity, No: SC015096
___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at: