Hardware / Software requirements for Array Server
From Array Suite Wiki
WARNING: This page addresses the hardware and software requirements for ArrayServer v11.2 or older. For updated information, please check Hardware/Software Requirements for OmicSoft Server
OmicSoft Server works with the client software (OmicSoft Viewer or OmicSoft Studio) to provide structural data repository, search and integration. To maximize the user experience, OmicSoft recommend the following hardware configuration for our server customers.
Item | OncoLand and/or DiseaseLand, or 2-4 analysis users | OncoLand/DiseaseLand+Single Cell Lands, or >4 analysis users | |
---|---|---|---|
Operating system (recommendations below) | Windows or Linux | Windows or Linux | AWS Cloud Option |
CPU | 4-8 cores (2.3G+) | 8-16 cores (2.3G+) | R5 generation recommended |
Memory (**1) | 32G+ | 64G+ recommended | |
Storage type | File server recommended | File server recommended | EBS and S3 |
Storage space (customer data) | 1TB | 3TB+ | S3 buckets |
Storage space (Resource files) | 300 GB | 500 GB | EBS storage |
Storage space (Lands) | 300 GB | 500 GB | EBS |
Networking (**4) | 1 GbE NIC | 1 GbE NIC | |
Recommended AWS EC2 class | r5.xlarge | r5.2xlarge |
To download all OncoLands and DiseaseLands (except Single Cell Lands), approximately 600GB of storage would be required, including the shared resource files for analysis.

- Baseline memory footprint is dependent on whether or not OmicSoft Lands are hosted on the server (~16GB for OmicSoft Server with all OmicSoft Lands), the numbers of platforms, and on the projects on the server.
- Additional memory is required for analysis; each NGS alignment job will take ~12GB memory to hold the genome index
- Two hard drives are strongly recommended for backup purpose. We suggest a backup at least every week. If one hard drive fails, it only takes one simple configuration change to connect the server to the other hard drive.
- Networking speed between server and clients are largely dependent on the server upload/download speed.
Contents |
Supported Linux Installations
OmicSoft Server v11.2 (May 2021 release) has been deployed using mono 6 on Ubuntu 20.04 (LTS).
OmicSoft Server v11.1 has been deployed using mono-4.0.4 on CentOS6 (with sqlite fix below) and CentOS7, Ubuntu 14 and Ubuntu 16, and RHEL7.
OmicSoft Server v10 has been deployed using mono-4.0.4 on CentOS 6/7, Ubuntu 14 and Ubuntu 16, and RHEL7.
Array Server can not load platforms (sqlite.interopp.dll issue)
If you're updating your server on CentOS6 or RHEL6, you may see the following message, preventing the server from starting:
Error occurred, message=Array Server can not load platforms. Message = SQLite.Interopp.dll
For customers using CentOS or RedHat Enterprise Linux version 6.*, if they can't upgrade the OS to a newer version, in order to use Array Studio >= 11.0.0.25, it is necessary to:
- remove the default libSQLite.Interop.dll from the arrayserver directory (make a backup just in case)
- download the custom libSQLite.Interop.so from this location
- copy the custom libSQLite.Interop.so in the arrayserver directory (ex. /opt/arrayserver/ )
Supported Windows Installations
OmicSoft Server has been deployed on Windows on Windows Server 2012, Windows Server 2016, and Windows 10.
Other Requirements / Suggestions
- The performance of the server is largely determined by the I/O speed. Therefore, we do not recommend USB external hard drives. Local hard drives or file servers are strongly recommended. File servers with parallel I/O support will have the best performance.
- We recommend incremental backup because most of the data managed by the server will not be changed after publishing.
OmicSoft Server can also be installed on a Cloud virtual machine as long as the above specs are met; OmicSoft Server can also be hosted on a cluster.
Required network connections
OmicSoft Server and OmicSoft Studio use the same connections to certain external resources such as NCBI and AWS. Please review these firewall permissions and make sure that your OmicSoft Server and EC2 compute instances can make outgoing connections to these resources.