<commit_before>---
title: Hardware sizing guidelines
menu:
  influxdb_1_7:
    weight: 40
    parent: Guides
---

Review configuration and hardware guidelines for InfluxDB OSS (open source) and InfluxDB Enterprise:

* [Single node or cluster?](/influxdb/v1.7/guides/hardware_sizing/#single-node-or-cluster?)
* [Queries guidelines](#queries-guidelines)
* [Single node guidelines](#single-node-guidelines)
* [Cluster guidelines](#cluster-guidelines)
* [When do I need more RAM?](#when-do-i-need-more-ram)
* [Recommended cluster configurations](#recommended-cluster-configurations)
* [Storage: type, amount, and configuration](#storage-type-amount-and-configuration)

## Single node or cluster?

If you need a single node instance of InfluxDB that's fully open source without redundancy, InfluxDB OSS works. (Without redundancy means if the server is unavailable, writes and queries immediately fail.)

If you need high-availability and redundancy, InfluxDB Enterprise offers multiple nodes (called a cluster). Multiple copies of data are distributed across multiple servers, so the loss of one server doesn't significantly impact the cluster.

If your performance requires at least one of the following:

- > 750,000 writes per second
- > 100 moderate queries
- > 10,000,000 unique series

We recommend a cluster to distribute the load among multiple servers. Performance at this scale on a single node may not be achievable. Please contact us at <<EMAIL>> for assistance tuning your systems.

## Queries guidelines

Queries complexity varies widely on system impact. Recommendations for both single nodes and clusters are based on **moderate** query loads. For **simple** or **complex** queries, we recommend testing and adjusting the suggested requirements as needed. Query complexity is defined by the following criteria:

|Query complexity| Criteria|
|----------------|----------|
|Simple          | Have few or no functions and no regular expressions|
|                | Are bounded in time to a few minutes, hours, or maybe a day|
|                | Typically execute in a few milliseconds to a few dozen milliseconds|
|Moderate queries| Have multiple functions and one or two regular expressions|
|                | May also have complex `GROUP BY` clauses or sample a time range of multiple weeks|
|                | Typically execute in a few hundred or a few thousand milliseconds|
|Complex queries | Have multiple aggregation or transformation functions or multiple regular expressions
|                | May sample a very large time range of months or years|
|                | Typically take multiple seconds to execute|

If your performance requirements fall into the **moderate** or **low** [load ranges](#load-ranges), you can likely use a single node instance of InfluxDB.
<commit_msg>rewrite single node or cluster section<commit_after>---
title: Hardware sizing guidelines
menu:
  influxdb_1_7:
    weight: 40
    parent: Guides
---

Review configuration and hardware guidelines for InfluxDB OSS (open source) and InfluxDB Enterprise:

* [Single node or cluster?](/influxdb/v1.7/guides/hardware_sizing/#single-node-or-cluster?)
* [Queries guidelines](#queries-guidelines)
* [Single node guidelines](#single-node-guidelines)
* [Cluster guidelines](#cluster-guidelines)
* [When do I need more RAM?](#when-do-i-need-more-ram)
* [Recommended cluster configurations](#recommended-cluster-configurations)
* [Storage: type, amount, and configuration](#storage-type-amount-and-configuration)

## Single node or cluster?

If your InfluxDB performance requires at least one of the following:

- > 750,000 writes per second
- > 100 moderate queries
- > 10,000,000 unique series

A single node may not support performance at this scale. We recommend InfluxDB Enterprise, which supports multiple nodes (a cluster) of servers. InfluxDB Enterprise distributes multiple copies of your data across a cluster, providing high-availability and redundancy——a server down doesn't significantly impact the cluster. Please contact us at <<EMAIL>> for assistance tuning your system.

If you want a single node instance of InfluxDB that's fully open source without redundancy, InfluxDB OSS (open source) works. (Without redundancy means if the server is unavailable, writes and queries immediately fail.)

## Queries guidelines

Queries complexity varies widely on system impact. Recommendations for both single nodes and clusters are based on **moderate** query loads. For **simple** or **complex** queries, we recommend testing and adjusting the suggested requirements as needed. Query complexity is defined by the following criteria:

|Query complexity| Criteria|
|----------------|----------|
|Simple          | Have few or no functions and no regular expressions|
|                | Are bounded in time to a few minutes, hours, or maybe a day|
|                | Typically execute in a few milliseconds to a few dozen milliseconds|
|Moderate queries| Have multiple functions and one or two regular expressions|
|                | May also have complex `GROUP BY` clauses or sample a time range of multiple weeks|
|                | Typically execute in a few hundred or a few thousand milliseconds|
|Complex queries | Have multiple aggregation or transformation functions or multiple regular expressions
|                | May sample a very large time range of months or years|
|                | Typically take multiple seconds to execute|

If your performance requirements fall into the **moderate** or **low** [load ranges](#load-ranges), you can likely use a single node instance of InfluxDB.

{'fraction_non_alphanumeric': 0.07956374038977293, 'fraction_numerical': 0.008224566422313607, 'mean_word_length': 3.9768683274021353, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 13, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3130325', 'n_tokens_mistral': 1425, 'n_tokens_neox': 1287, 'n_words': 677}