Open GoogleCodeExporter opened 9 years ago
Updating to 2.3.0e did the trick...or so I thought.
For a couple of seconds I saw STAR using 5900% CPU (=59 Cores)
now (for the majority of the mapping time) it is down to 500% (=5 CPU cores)
...
Original comment by goo...@schwarzelan.de
on 24 Feb 2014 at 4:11
To be more concise:
With an imput of 2x12.5 mio sequences, STAR runs on 60 cores, for about a
minute,
summing up 60-70 minutes of CPU time,
afterwards its slowgoing with 5 threads, until it is hitting the 120 minutes of
CPUTime,
followed by another number of minutes in single-threaded mode.
Original comment by goo...@schwarzelan.de
on 24 Feb 2014 at 4:42
Please post your questions in the STAR forum
https://groups.google.com/d/forum/rna-star for a faster reply.
As you increase the number of threads, the main limiting factor is the disk I/O
bandwidth, especially writing of the SAM files. If you have enough RAM, please
try running STAR from the /dev/shm/ virtual disk (both input and output files).
This would give us an idea what portion of slowdown is caused by the disk
bandwidth.
Original comment by adobin@gmail.com
on 25 Feb 2014 at 10:23
Original issue reported on code.google.com by
goo...@schwarzelan.de
on 24 Feb 2014 at 1:25