Estimating Disk Space Utilization on the MiSeq i100 Series
Last updated
Last updated
© 2023 Illumina, Inc. All rights reserved. All trademarks are the property of Illumina, Inc. or their respective owners. Trademark information: illumina.com/company/legal.html. Privacy policy: illumina.com/company/legal/privacy.html
Background
This guide provides disk space usage estimates for sequencing runs on the MiSeq i100 Series. The calculations are based on key parameters such as flow cell size, run type, read length, and data quality. The estimates encompass both BCL (Base Call) file sizes and compressed FASTQ file sizes, ensuring accurate resource planning for sequencing projects.
Key Parameters
The following tables provide disk space utilization estimates for the following flow cell and run configurations.
Flow Cell Types
5M
25M
50M
100M
Run Types and Read Length
2x151: Paired-end reads, 302 cycles in total.
2x300: Paired-end reads, 600 cycles in total.
Disk Usage Estimates
The table below summarizes the estimated disk usage for different sequencing configurations on the MiSeq i100 Series:
Key Insights
BCL File Sizes: These are proportional to the number of reads generated and vary based on the flow cell size and read length.
For smaller runs (5M flow cell), disk usage is minimal (~0.84 GB for 2x151).
For larger runs (100M flow cell), usage scales significantly (~33.23 GB for 2x300).
Compressed FASTQ Sizes
FASTQ files are the compressed output of sequencing reads, and their sizes are generally 25-30% larger than the corresponding BCL files.
FASTQ file size varies considerably depending on DRAGEN or GZIP compression format.
Planning Recommendations:
Ensure adequate storage for both raw (BCL) and processed (FASTQ) files.
For high-throughput runs (e.g., 100M flow cells with 2x300 reads), allocate at least 40-50 GB of disk space per run.
Conclusion
This guide provides essential estimates for disk space usage on the MiSeq i100 Series, helping labs optimize storage requirements and ensure smooth sequencing operations. For specific workflows or extended configurations, additional considerations may apply.
For any feedback or questions regarding this article (Illumina Knowledge Article #9356), contact Illumina Technical Support techsupport@illumina.com.