<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?](#single-node-or-cluster)
* [Query guidelines](#query-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:

- more than 750,000 writes per second
- more than 100 moderate queries
- more than 10,000,000 unique series
- complex queries (span months/years or include multiple transformations, aggregations)

A single node may not support performance at this scale. We recommend InfluxDB Enterprise, which supports multiple data nodes (a cluster) across multiple server cores. InfluxDB Enterprise distributes multiple copies of your data across a cluster, providing high-availability and redundancy, so an unavailable node 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, requires fewer writes, queries, and unique series than listed above, and do **not require** redundancy, we recommend InfluxDB OSS (open source).

> **Note:** Without the redundancy of a cluster, writes and queries fail immediately when a server is unavailable.

## Query guidelines

> Query 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                                                                              |
|------------------|---------------------------------------------------------------------------------------|
|                  | Are bounded in time to a few minutes, hours, or maybe a day                           |
| Simple           | Have few or no functions and no regular expressions                                   |
| Complex queries  | Have multiple aggregation or transformation functions or multiple regular expressions |
| 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     |
|                  | May sample a very large time range of months or years                                 |
|                  | Typically execute in a few hundred or a few thousand milliseconds                     |
|                  | Typically execute in a few milliseconds to a few dozen milliseconds                   |
|                  | Typically take multiple seconds to execute                                            |

## Single node guidelines

Run InfluxDB on locally attached solid state drives (SSDs). Other storage configurations have lower performance and may not be able to recover from small interruptions in normal processing.<commit_msg>fix query complexity table<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?](#single-node-or-cluster)
* [Query guidelines](#query-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:

- more than 750,000 writes per second
- more than 100 moderate queries
- more than 10,000,000 unique series
- complex queries (span months/years or include multiple transformations, aggregations)

A single node may not support performance at this scale. We recommend InfluxDB Enterprise, which supports multiple data nodes (a cluster) across multiple server cores. InfluxDB Enterprise distributes multiple copies of your data across a cluster, providing high-availability and redundancy, so an unavailable node 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, requires fewer writes, queries, and unique series than listed above, and do **not require** redundancy, we recommend InfluxDB OSS (open source).

> **Note:** Without the redundancy of a cluster, writes and queries fail immediately when a server is unavailable.

## Query guidelines

> Query 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         | 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          | 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                                            |

## Single node guidelines

Run InfluxDB on locally attached solid state drives (SSDs). Other storage configurations have lower performance and may not be able to recover from small interruptions in normal processing.
{'fraction_non_alphanumeric': 0.08748728382502544, 'fraction_numerical': 0.006103763987792472, 'mean_word_length': 2.4478957915831665, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 12, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5555591', 'n_tokens_mistral': 1526, 'n_tokens_neox': 1375, 'n_words': 756}