Skip to main content

Table 4 Runtime and memory (rss) evaluation of gedi, smufin and mutect

From: GeDi: applying suffix arrays to increase the repertoire of detectable SNVs in tumour genomes

DatasetSize (Million reads / GB)RSS (GB)Runtime (hours:minutes)
  GeDi (no emfilter)MuTectSMuFin (256 thread)GeDi (no emfilter)MuTectSMuFin (256 thread)
SMuFin:chr2226 / 4.4016 (19)6722 (107)0:20 (0:30)1:3317:48 (3:47)
TSD:chr1711 / 2.43767-0:060:50-
TSD:chr224 / 0.873108-0:020:38-
MB:L.A2052 / 69.21101797*-71:391800*-
  1. no emfilter (bracketed values for gedi) shows gedi’s resource requirements when emfilter is off, for all other gedi runs, emfilter is on. 256 thread (bracketed values for smufin) shows smufin’s resource requirements when run with suggested command at, whilst values without brackets show SMuFin’s requirements when run with 32 logical threads. GeDi and MuTect were always run with 32 logical threads, apart from analysis of MB:L.A where 64 logical threads were used for both callers. A full description of the methods used to perform this benchmark are provided in Additional file 1: Method 4. All analyses were performed on the same computing system with Xeon: E5-4650v2 CPUs. Runtime and RSS was recorded using GNU Time 1.7 (, where runtime is the elapsed wall clock time and RSS is the maximum residency set size. Asterisk values: MuTect took 72 hours (maximum user runtime) on our system to analyse 4% of the human genome (percentage along genome is given in MuTect output). Accordingly, assuming uniform coverage of MB:L.A data across the genome, we estimated MuTect’s runtime in hours for analysis of the complete MB:L.A dataset by multiplying 72 by 25