Special requirements for read mapping. The Read mapper requires CPU with an AVX instruction set.
The numbers below give minimum and recommended memory for systems running mapping and analysis tasks. The requirements suggested are based on the genome size.
Special requirements for de novo assembly. De novo assembly may need more memory than stated above – this depends both on the number of reads, error profile and the complexity and size of the genome. See our white paper on de novo assembly for examples of the memory usage of various data sets.
The QIAGEN CLC Workbenches are built using Java technology. If you are a Windows, Mac OS X or Linux user, the QIAGEN CLC Workbench includes a JRE (Java Runtime Environment) which is needed to run the QIAGEN CLC Workbench. This JRE will not interfere with existing JRE’s on your computer and will only be used to run the QIAGEN CLC Workbench.
Mac and the Mac logo are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Microsoft, Windows and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.
Special requirements for read mapping. The numbers below give minimum and recommended memory for systems running mapping and analysis tasks. The requirements suggested are based on the genome size.
Special requirements for de novo assembly. De novo assembly may need more memory than stated above – this depends both on the number of reads, error profile and the complexity and size of the genome. See our white paper on de novo assembly for examples of the memory usage of various data sets.
The license server does not require much in terms of processing power and it only consumes a few megabytes of memory. This means that if you are putting together a dedicated server specifically for use as a license server, a modestly powered system equipped with a high number of redundant components will probably be a better investment than a system which is faster, has more memory, etc.
The system requirements for the CLC License Server are:
The CLC License Server is based on the LM-X License Manager. The list of systems above has been derived from the LM-X supported system list. The CLC License Server will likely work on other Windows, Linux and (newer) macOS systems, but we cannot guarantee this.
The numbers below give minimum and recommended amounts for systems running mapping and analysis tasks. The requirements suggested are based on the genome size.
Human (3.2 gigabases) and Mouse (2.7 gigabases)
De novo assembly may need more memory than stated above – this depends both on the number of reads and the complexity and size of the genome. See our white paper on de novo assembly for examples of the memory usage of various data sets.
Analysis on the QIAGEN CLC Genomics Server can be initiated from:
*Only server-enabled tools on the QIAGEN CLC Main Workbench can be launched from that client to run on the QIAGEN CLC Genomics Server.
The system requirements of Biomedical Genomics Analysis are the same as those for the CLC Genomics Workbench apart from the following:
To work with CLC Single Cell Analysis Module you will need to have CLC Genomics Workbench 21.0 installed on your computer. With the exception of the requirements below, the system requirements of CLC Single Cell Analysis Module are the same as those for CLC Genomics Workbench (http://resources.qiagenbioinformatics.com/manuals/clcgenomicsworkbench/current/index.php?manual=System_requirements.html)
For mapping of reads, we recommend running on a server. Although a laptop with 16 GB of RAM can be used, the large number of reads are likely to lead to long runtimes when there are more than 1000 cells.
In principle, the remaining tools can be run on modest hardware such as a laptop, especially when the number of cells is under 50,000.
The Long Read Support (beta) requires a CPU with an AVX instruction set due to extensive use of the following open-source tools:
To work with CLC Microbial Genomics Module you will need to have CLC Genomics Workbench version 21 installed on your computer. With exception of the requirements below, the system requirements of CLC Microbial Genomics Module 21.0 are the same as the ones required for the CLC Genomics Workbench (http://resources.qiagenbioinformatics.com/manuals/clcgenomicsworkbench/current/index.php?manual=System_requirements.html)
Special requirements for the Large MLST Scheme tools. The system requirements for the Large MLST Scheme tools depend on the size of the MLST schemes (both the number of alleles and the number of sequence types). A laptop with 16GB of memory is normally sufficient for 7-gene schemes or cgMLST schemes based on a moderate number of isolates. Typing or constructing larger schemes may require more memory, and in general, we recommend at least 64GB of memory when working with cg/wgMLST schemes based on more than 100 isolates.
Special requirements for the Taxonomic Profiler. The quality performance of the Taxonomic Profiler depends on the reference database used – the more complete a database, the better the quality. However, running the Taxonomic Profiler with a given database size will require at least the same amount of memory. For example, running with a 14 GB database requires at least 16 GB of RAM, and running with a 56 GB database requires a minimum of 64 GB RAM. When creating your reference database with the Download Microbial Reference Database tool, you will get a warning about the memory requirements needed for running the Taxonomic Profiler with this database.
Special requirements for De Novo Assemble Metagenome. It is recommended to have at least 16 GB RAM when running the De Novo Assemble Metagenome.
The PCoA 3D viewer requirements are the same as the 3D Molecule Viewer.
The Sunburst viewer makes use of JavaFX and may not work on older Linux kernels. An updated list of requirements for JavaFX can be found at http://www.oracle.com/technetwork/java/javafx/downloads/supportedconfigurations-1506746.html.
All the system requirements on this page are requirements for the most recent versions of the products. For requirements for older versions, please refer to the user manual for that specific version.
