mirrors/scylladb
1
0
Fork 0
mirror of https://github.com/scylladb/scylladb.git synced 2026-05-28 10:41:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge 'doc: update ScyllaDB requirements - supported CPUs and AWS i4g instances' from Anna Stuchlik

Browse Source 
Fix https://github.com/scylladb/scylla-docs/issues/4144

Closes #11226

* github.com:scylladb/scylladb:
  Update docs/getting-started/system-requirements.rst
  doc: specify the recommended AWS instance types
  doc: replace the tables with a generic description of support for Im4gn and Is4gen instances
  doc: add support for AWS i4g instances
  doc: extend the list of supported CPUs
This commit is contained in:
Botond Dénes
2022-11-16 08:15:00 +02:00
parent bd1fcbc38f d2e54f7097
commit e90d0811d0
1 changed files with 28 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/getting-started/system-requirements.rst
View File

@@ -30,14 +30,19 @@ ScyllaDB tries to maximize the resource usage of all system components. The shar
CPU
^^^
ScyllaDB requires modern Intel CPUs that support the SSE4.2 instruction set and will not boot without it.
The following CPUs are supported by Scylla:
ScyllaDB requires modern Intel/AMD CPUs that support the SSE4.2 instruction set and will not boot without it.
* Intel core: Westmere or later (2010)
* Intel atom: Goldmont or later (2016)
* AMD low power: Jaguar or later (2013)
* AMD standard: Bulldozer or later (2011)
ScyllaDB supports the following CPUs:
* Intel core: Westmere and later (2010)
* Intel atom: Goldmont and later (2016)
* AMD low power: Jaguar and later (2013)
* AMD standard: Bulldozer and later (2011)
* Apple M1 and M2
* Ampere Altra
* AWS Graviton, Graviton2, Graviton3
In terms of the number of cores, any number will work since ScyllaDB scales up with the number of cores.
@@ -108,20 +113,25 @@ Cloud Instance Recommendations
Amazon Web Services (AWS)
--------------------------------
* The recommended instance types are :ref:`i3 <system-requirements-i3-instances>`, :ref:`i3en <system-requirements-i3en-instances>`, and :ref:`i4i <system-requirements-i4i-instances>`.
* We recommend using enhanced networking that exposes the physical network cards to the VM.
.. note::
Some of the ScyllaDB configuration features rely on querying instance metadata.
Disabling access to instance metadata will impact using Ec2 Snitches and tuning performance.
See `AWS - Configure the instance metadata options <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-options.html>`_ for more information.
.. _system-requirements-i3-instances:
We highly recommend EC2 **I3** instances—High I/O. This family includes the High Storage Instances that provide very fast SSD-backed instance storage optimized for very high random I/O performance and provide high IOPS at a low cost. We recommend using enhanced networking that exposes the physical network cards to the VM.
i3 instances
^^^^^^^^^^^^
This family includes the High Storage Instances that provide very fast SSD-backed instance storage optimized for very high random I/O performance and provide high IOPS at a low cost. We recommend using enhanced networking that exposes the physical network cards to the VM.
i3 instances are designed for I/O intensive workloads and equipped with super-efficient NVMe SSD storage. It can deliver up to 3.3 Million IOPS.
An i3 instance is great for low latency and high throughput, compared to the i2 instances, the i3 instance provides storage that it's less expensive and denser along with the ability to deliver substantially more IOPS and more network bandwidth per CPU core.
i3 instances
^^^^^^^^^^^^
=========================== =========== ============ =====================
Model vCPU Mem (GB) Storage (NVMe SSD)
=========================== =========== ============ =====================
@@ -144,6 +154,8 @@ Source: `Amazon EC2 I3 Instances <https://aws.amazon.com/ec2/instance-types/i3/>
More on using ScyllaDB with `i3.metal vs i3.16xlarge <https://www.scylladb.com/2018/06/21/impact-virtualization-database/>`_
.. _system-requirements-i3en-instances:
i3en instances
^^^^^^^^^^^^^^
i3en instances have up to 4x the networking bandwidth of i3 instances, enabling up to 100 Gbps of sustained network bandwidth.
@@ -179,12 +191,12 @@ All i3en instances have the following specs:
See `Amazon EC2 I3en Instances <https://aws.amazon.com/ec2/instance-types/i3en/>`_ for details.
.. _system-requirements-i4i-instances:
i4i instances
^^^^^^^^^^^^^^
i4i support is available for ScyllaDB Open Source 5.0 and later and ScyllaDB Enterprise 2021.1.10 and later.
=========================== =========== ============ =====================
Model vCPU Mem (GB) Storage (NVMe SSD)
=========================== =========== ============ =====================
@@ -205,7 +217,7 @@ i4i.32xlarge 128 1,024 8 x 3,750 GB
i4i.metal 128 1,024 8 x 3,750 GB
=========================== =========== ============ =====================
All i41 instances have the following specs:
All i4i instances have the following specs:
* 3.5 GHz all-core turbo Intel® Xeon® Scalable (Ice Lake) processors
* 40 Gbps bandwidth to EBS in the largest size and up to 10 Gbps in the four smallest sizes (twice that of i3 instances. Up to 75 Gbps networking bandwidth (three times more than I3 instances).
@@ -218,6 +230,10 @@ See `ScyllaDB on the New AWS EC2 I4i Instances: Twice the Throughput & Lower Lat
learn more about using ScyllaDB with i4i instances.
Im4gn and Is4gen instances
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ScyllaDB supports Arm-based Im4gn and Is4gen instances. See `Amazon EC2 Im4gn and Is4gen instances <https://aws.amazon.com/ec2/instance-types/i4g/>`_ for specification details.
Google Compute Engine (GCE)
-----------------------------------