Before you create a Lindorm instance, select various configurations that can meet your business requirements based on factors such as business scenarios, workloads, and prices. This topic describes how to select an engine, a storage type, a node specification, and the number of nodes for a Lindorm instance.

Select an engine

Lindorm supports multiple engines and is compatible with the standard APIs of various open source software and services. It also supports SQL queries and provides capabilities such as time series processing and text retrieval and analysis. Different engines are suitable for different business scenarios. You can select one or more engines based on your business requirements. For more information, see Engines.

Select a storage type

Lindorm uses LindormStore to decouple storage from computing. Multiple engines of a Lindorm instance can share the storage capacity. The data access latency varies based on the storage type. For more information, see Storage types.

Select a node specification and the number of nodes

Before you select a node specification and the number of nodes for a selected engine, determine the read workloads and write workloads of your business. The following table describes the suggestions on how to select a node specification and the number of nodes. We recommend that you use these suggestions only if the data size of each request is up to 10 KB and no complex queries are performed.
Transactions per second (TPS) and queries per second (QPS) Node specification and number of nodes Business scenario
0~1000 2 nodes with the specification of 4 cores and 16 GB memory. Suitable for database access in low-load scenarios. The minimum specification is 4 cores and 8 GB memory. We recommend that you do not select the minimum specification because the memory capacity that is provided by this specification cannot meet your business requirements in most cases. If you select the minimum specification, service stability cannot be ensured during peak hours or when a large amount of data is requested. For example, a memory overflow may occur or tasks may be terminated.
1000~20000 2 to 3 nodes with a specification of 8 cores and 32 GB memory. Suitable for database access in low-and medium-load scenarios. Compared with the specification of 8 cores and 16 GB memory, the specification of 8 cores and 32 GB memory is more cost-effective, and the memory capacity is increased by two times. This helps ensure higher stability.
> 20,000 Select one of the following specifications: 8 cores and 32 GB memory, 16 cores and 32 GB memory, 16 cores and 64 GB memory, 32 cores and 64 GB memory, and 32 cores and 128 GB memory.

Select the number of nodes based on the access mode and traffic on your business application.

Specifications that provide a large memory capacity are suitable for the following scenarios:
  • If your business application is deployed online, we recommend that you select a specification for your instance that provides a large memory capacity. This way, you can improve system performance.
  • If you want to run heavy-load tasks offline such as MapReduce tasks and Spark tasks or the TPS and QPS are very high, we recommend that you select a specification for your instance that provides a large memory capacity.
Note All node specifications supported by Lindorm are dedicated specifications. A dedicated Lindorm instance exclusively occupies all CPU and memory resources that are allocated to it. The performance of a dedicated Lindorm instance remains stable and is not affected by the other instances that are deployed on the same physical server.

When you select a node specification and the number of nodes for a selected engine, you also need to consider other factors in addition to the read and write workloads. If you need technical support to select instance configurations when you create a Lindorm instance, .

FAQ

When I purchase a Lindorm instance, do I need to select a higher specification and fewer nodes or a lower specification and more nodes if both options can meet my business requirements?

We recommend that you select a higher specification and fewer nodes for your Lindorm instance. Lindorm supports unlimited horizontal scaling capabilities. If access requests are evenly distributed among nodes, you can add nodes to mitigate issues such as heavy loads, high latency, and service jitters. If a large amount of data is requested or data is frequently accessed in a short period of time, the specification of a single node determines the capability that is required to handle hotspotting issues. In this case, a higher node specification provides strong anti-jitter capabilities and ensures higher overall service stability.

If you want to upgrade the node specifications of a Lindorm instance, you can upgrade the specifications in the Lindorm console. For more information, see Change the engine specification of an instance.