Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • xinchen
    Junior Member
    • May 2010
    • 6

    TopHat approximate run time & memory usage?

    Hi everyone,

    I'm using TopHat to map my RNA-seq reads to splice junctions for use in Cufflinks, but it's been taking a bit longer than I expected. One sample I ran (as an initial test) has been going for ~34 hours, and the tophat_out folder is using up around 76 GB of space. By looking in the logs, it seems to be on the "segment_juncs" step.

    Each of the individual samples I hope to align have roughly 90 million reads (@ 50 nt) over 3 lanes, and I'm aligning to the human genome (hg19).

    Would anyone know how long I should expect the program to run for, and also how much disk space it'll need per sample?

    Thanks!

    edit: I'm using single-end reads
    Last edited by xinchen; 05-16-2010, 07:06 PM.
  • shurjo
    Senior Member
    • Jan 2009
    • 132

    #2
    It routinely takes ~40 hours for me (~45 million reads, with - p 4 to use four threads and 16G RAM). It will delete the huge temp files it generates, so the disk usage may not be that much of any issue.

    Comment

    • sphil
      Senior Member
      • Apr 2010
      • 192

      #3
      I'm not sure but i think that TopHat need for 75million reads about 3 Days...

      Comment

      • xinchen
        Junior Member
        • May 2010
        • 6

        #4
        Thanks! It ended up taking ~50 hours for my test sample, which isn't too long

        Comment

        • ymc
          Senior Member
          • Mar 2010
          • 496

          #5
          How can you guys compare run time and memory usage without stating the CPU and RAM you are using???

          Comment

          Latest Articles

          Collapse

          • GATTACAT
            Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by GATTACAT
            Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
            Yesterday, 11:43 AM
          • SEQadmin2
            Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by SEQadmin2


            I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

            Here are nine questions we think about, in roughly the order they matter, before...
            06-18-2026, 07:11 AM

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, Today, 11:08 AM
          0 responses
          6 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          11 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          19 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-17-2026, 06:09 AM
          0 responses
          53 views
          0 reactions
          Last Post SEQadmin2  
          Working...