Skip to content

IsoQuant 3.4.2
Compare
Choose a tag to compare
@andrewprzh andrewprzh released this 13 Jul 20:47
v3.4.2
c097f52

  • Dramatically reduce RAM consumption. Should fix #209.

    IsoQuant 3.4.2 was tested on a simulated ONT dataset with 30M reads using 12 threads. In the default mode RAM consumption decreased from 280GB to 12GB when using the reference annotation and from 230GB down to 6GB in the reference-free mode. Running time in the default mode increased by approximately 20-25%. When using --high_memory option, running time remains the same as in 3.4.1, RAM consumption in the reference-based mode is 46GB, and 36GB in the reference-free mode. Note, that in general RAM consumption depends on the particular data being used and the number of threads.

    In brief, in 3.4.0 and 3.4.1 inadequate RAM consumption was caused by this commit. Apparently, adding a couple of int fields to the BasicReadAssignment class made the default pickle serialization not to clean used memory (possibly, a leak). Since some large lists of BasicReadAssignment were sent between processes, this caused the main process to consume unnecessary RAM. When later new processes were created for GTF construction, total RAM consumption exploded thanks to the way Python multiprocessing works. This release implements two ways fixing the issue: sending objects via disk (default) and using custom pickle serialization (when --high_memory is used).

  • Transcript and exon ids are now identical between runs, including ones with different number of threads.

Assets 3
Loading