WGS germline pipeline stages on CPU, GPU and DRAGEN (Samarakoon et al. 2025)
Direct evidenceIndependent study: Reported in a study whose authors did not develop the evaluated tool.Runtime (lower is better), with the other metrics below each value. The best value in each column is highlighted.
| Tool | Read mapping | HaplotypeCaller or GSVC calling | DeepVariant calling | Mapping plus HaplotypeCaller or GSVC |
|---|---|---|---|---|
DRAGENconventional | 14.08 min (best in column)NA12778 (9.82x) | 7.84 minNA12778 (9.82x) | Not reported | 21.92 minNA12778 (9.82x) |
| 14.15 minNA12778 (9.82x) | 4.87 min (best in column)NA12778 (9.82x) | 6.08 minNA12778 (9.82x) | 19.02 min (best in column)NA12778 (9.82x) | |
| 334.20 minNA12778 (9.82x) | 613.88 minNA12778 (9.82x) | 337.75 minNA12778 (9.82x) | 948.08 minNA12778 (9.82x) |
Caveats and method
What each column measures:
- Read mapping: Wall-clock minutes for the read mapping stage on ten WGS samples for CPU-only GATK, Parabricks on L4, A100 and H100 GPUs, and DRAGEN v4.2
- HaplotypeCaller or GSVC calling: Wall-clock minutes for the HaplotypeCaller or DRAGEN GSVC calling stage on ten WGS samples for CPU-only GATK, Parabricks on L4, A100 and H100 GPUs, and DRAGEN v4.2
- DeepVariant calling: Wall-clock minutes for the DeepVariant calling stage on ten WGS samples for CPU-only DeepVariant and Parabricks DeepVariant on L4, A100 and H100 GPUs
- Mapping plus HaplotypeCaller or GSVC: Wall-clock minutes for the total of read mapping and HaplotypeCaller or DRAGEN GSVC on ten WGS samples for CPU-only GATK, Parabricks on L4, A100 and H100 GPUs, and DRAGEN v4.2
- One run per sample and configuration; no repeats or variance printed.
- Hardware differs between columns (CPU cluster, two GCP VMs, an HPC GPU node and a DRAGEN server), so differences mix software and hardware.
- CPU-only nodes were shared with other users; GCP VMs ran in a multi-tenant environment (Table S2 notes).
- DRAGEN mapping time was assembled from three process logs because its processes run concurrently (Methods 2.4).
- No linked source repeats runs, measures run-to-run concordance of the calls, or reports accuracy next to runtime, so this evidence bears on the resource and throughput part of the question only, not on reproducibility.
- Hardware differs between columns (CPU cluster, two GCP VMs and an HPC GPU node), so differences mix software and hardware.
- DRAGEN has no DeepVariant stage; its column prints NA and has no evaluation.
- Total is the sum of read mapping and HaplotypeCaller or GSVC stages; DeepVariant is excluded. The NA12778 L4 total (117.59) does not equal its stage values (26.02 + 5.92 = 31.94); that result is disputed and not shown.
Protocols: WGS germline pipeline wall-clock, read mapping stage (Samarakoon et al. 2025 Table S3a), WGS germline pipeline wall-clock, HaplotypeCaller or DRAGEN GSVC calling stage (Samarakoon et al. 2025 Table S3b.1), WGS germline pipeline wall-clock, DeepVariant calling stage (Samarakoon et al. 2025 Table S3b.2), WGS germline pipeline wall-clock, total of read mapping and HaplotypeCaller or DRAGEN GSVC (Samarakoon et al. 2025 Table S3c)