# DNA seq paired-end read collection running slow (taking days)

**URL:** <https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696>\
**Category:** Uncategorized\
**Tags:** queued-gray-datasets\
**Created:** [May 15, 2020, 5:24pm UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696 "2020-05-15T17:24:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zrs1](https://avatars.discourse-cdn.com/v4/letter/z/f07891/32.png) [@zrs1](https://help.galaxyproject.org/u/zrs1)\
**Post date:** [May 15, 2020, 5:24pm UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/1 "2020-05-15T17:24:41Z")

</div>

I’m have been trying to map a collection of 96 paired-end fastqsanger files onto a human genome using BWA-MEM. I’ve also tried Bowtie2, and map with minimap2. Reads were trimmed using trimmomatic. I’ve been trying for a couple days to run these jobs and wondering if there is a faster way to do this or if I’m doing anything wrong?

-Z

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [May 16, 2020, 12:28am UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/2 "2020-05-16T00:28:18Z")

</div>

Hi @zrs1

When using public Galaxy servers (or really, any Galaxy server), it is best to leave queued jobs queued. Each will start up as resources become available. Avoid deleting and restarting, unless you need to modify inputs/settings, or you’ll lose the original placements in the job queue, further extending wait time.

The [usegalaxy.org](http://usegalaxy.org/) server and many other public servers are very busy right now. Mapping jobs require the use of larger cluster nodes which tend to be the busiest. It will take some time to process all 96 jobs.

More details about how jobs queue and execute are in this recent Q&A: [Job Stuck in Queue](https://help.galaxyproject.org/t/job-stuck-in-queue/3666)

Alternatives include setting up your own Galaxy server. These prior Q&A topics have basic details and link-outs to all options. A commercial cloud is not your only choice but does involve less administration/local resources. [Commercial servers -- Galaxy Choices](https://help.galaxyproject.org/t/commercial-servers-galaxy-choices/2647) && [Galaxy Cloudman or GVL?](https://help.galaxyproject.org/t/galaxy-cloudman-or-gvl/3651).

To find more Q&A about Galaxy choices, please search this forum with the keyword “choices” or “cloudman”.

Thanks!

---

<div class="post-metadata">

**Author:** ![zrs1](https://avatars.discourse-cdn.com/v4/letter/z/f07891/32.png) [@zrs1](https://help.galaxyproject.org/u/zrs1)\
**Post date:** [May 19, 2020, 6:18pm UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/3 "2020-05-19T18:18:05Z")

</div>

Thank you! I let it run for a day. All the jobs paused before completing and won’t restart when I resume them. I tried logging out and back in again. Do you know any way around this issue?

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [May 19, 2020, 6:58pm UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/4 "2020-05-19T18:58:47Z")

</div>

Hello,

There were some recent server issues at a few different public Galaxy servers that may have impacted your jobs.

However, a “paused job” (light blue with a link) usually indicates an input problem.

- Where are you working (URL if a public server)?
- Are the inputs intact (expand the datasets to check)? Metadata issues were presenting for a few hours yesterday at [usegalaxy.org](http://usegalaxy.org). How to check if this is your issue and what to do: [Getting an metadata error using any tool from Galaxy as 'An error occurred setting the metadata [Set it manually or retry auto-detection]. for this dataset'](https://help.galaxyproject.org/t/getting-an-metadata-error-using-any-tool-from-galaxy-as-an-error-occurred-setting-the-metadata-set-it-manually-or-retry-auto-detection-for-this-dataset/3724)
- Do the paused jobs have any other information about what is wrong? Warning messages?

A rerun may be the quickest solution if this was a server-side problem. But check the other items and let us know if you need more help. Where you are using Galaxy will matter for how to best proceed.

Thanks!

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [May 20, 2020, 12:40am UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/5 "2020-05-20T00:40:31Z")

</div>

**Update:** Additional server updates/fixes were applied in the last few hours at [https://usegalaxy.org](https://usegalaxy.org).

If your job failed, rerunning is the best/fastest option.

If a job newly started fails from this time point forward, please try a rerun but also let us know here. Please confirm this is the server where you are working in your reply. Including the error message is also helpful.

We sincerely apologize for the recent troubles!

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [December 22, 2023, 12:04am UTC](https://help.galaxyproject.org/t/dna-seq-paired-end-read-collection-running-slow-taking-days/3696/6 "2023-12-22T00:04:28Z")

</div>


