ColumnStore Minimum Hardware Specification
You are viewing an old version of this article. View
the current version here.
The following table outlines the minimum recommended production server specifications which can be followed for both on premise and cloud deployments:
Single Server
Item | Description |
---|---|
Physical Server | 4 core Intel / AMD, 32GB Memory |
Storage | Local disk with appropriate RAID redundancy or network attached storage |
Multi Server
Item | Description |
---|---|
UM Physical Server | 4 core Intel / AMD, 32GB Memory |
PM Physical Server | 4 core Intel / AMD, 16GB Memory |
Storage | Local disk on each PM can be appropriate for systems that can tolerate some down time in the event of server failure. To leverage the automated fail-over capabilities, a networked storage layer such as SAN for on premise or EBS in AWS is a better choice. A distributed filesystem such as the open source GlusterFS will also allow for node fail-over. |
Network Interconnect | In a multi server deployment data will be passed around via TCP/IP networking. At least a 1G network is recommended. |
Details
These are minimum recommendations and in general the system will perform better with more hardware:
- More CPU cores and servers will improve query processing response time.
- More memory will allow the system to cache more data blocks in memory.
- Faster network will allow data to flow faster between UM and PM nodes.
- Where it is an option, it is recommended to use bare metal servers for additional performance since ColumnStore will fully consume CPU cores and memory.
For AWS our own internal testing generally uses m4.4xlarge instance types as a cost effective middle ground. The R4.8xlarge has also been tested and performs about twice as fast for about twice the price.
For development purposes, the system will run on typical laptop / desktop hardware down to single core, 4gb memory.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.