It looks like you're new here. If you want to get involved, click one of these buttons!
I have a region which worked fine, but now doesn't seem to work. Here is a part of the run using version 2.5
17:66743059-81195210.it1hc.stdout-INFO 21:59:30,131 ProgressMeter - 17:73500213
17:66743059-81195210.it1hc.stdout-INFO 22:00:30,949 ProgressMeter - 17:73500549
17:66743059-81195210.it1hc.stdout-INFO 22:01:31,026 ProgressMeter - 17:73500549
17:66743059-81195210.it1hc.stdout-INFO 22:02:31,045 ProgressMeter - 17:73500549
17:66743059-81195210.it1hc.stdout:INFO 22:03:31,063 ProgressMeter - 17:73500593
17:66743059-81195210.it1hc.stdout-INFO 22:04:31,098 ProgressMeter - 17:73501295
As you can see it made it by 17:73500549 in about 3 minutes. I am rerunning the same BAMs in the same region with version 2.6, and now it has been stuck on 17:73500549 for >12 hours. Even when rerunning the same version I have noticed that usually runs take about the same time, but every so often are orders of magnitude longer. I am using -dcov 200, so I know there is some sampling variation (although in this region everyone is between 50-100 reads coverage), but a difference of 3 minutes to > 600 minutes seems excessive.
Any suggestions on making runtimes for regions more predictable?