# Network Configurations

Every Network Configuration comes with a different configuration in terms of the number of Nodes and computational power. The following table outlines available resource limitations based on the provisioned node's size and will help you understand what constitutes a Network Configuration.

| **Small**               | **Medium**              | **Large**               |
| ----------------------- | ----------------------- | ----------------------- |
| 1 Peer + 1 orderer node | 2 Peer + 1 orderer node | 4 Peer + 3 orderer node |
| 0.5 CPU                 | 1 CPU                   | 2 CPU                   |
| 1 GB RAM                | 2 GB RAM                | 4 GB RAM                |
| 20 req/sec              | 100 req/sec             | 1000 req/sec            |

\*The number of nodes mentioned above is the default number of nodes for each network size. It is recommended to have a total of at least 3 orderer nodes in the entire network for production deployments.

\*\*The req/sec mentioned above are indicative numbers and the actual performance of a network depends on various factors like the number of organizations, channels, endorsement policies, the performance of chaincode, etc.

Learn more about Nodes: [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca.md)

{% hint style="info" %}
Spydra allows users to add a custom number of nodes while creating Network, joining a Network, or later on from the Node page. It is recommended to have an odd number of Orderer nodes for consensus. <br>

[Why is it recommended to have an Odd number of Orderer nodes on a Network?](/support/why-is-it-recommended-to-have-an-odd-number-of-orderer-nodes-on-a-network.md)
{% endhint %}

{% hint style="info" %}
Only organizations that have a Network Admin role will be able to add Orderer Nodes. This can be used to limit which organizations should be able to participate in the network consensus.
{% endhint %}

{% hint style="info" %}
Changing the Network Configuration will also affect your Organization's pricing. Please learn more about the pricing here. \
\
[Pricing](/billing-and-pricing/pricing.md)
{% endhint %}

## How to Choose Network Configurations?

You can choose a Node Configuration based on your requirement and the limitations of the Network Configurations.

If you are still unsure about how to go about it, we recommend you choose the Network Configuration based on the below illustration.&#x20;

* Proof of Concepts / Testing - **Small Networks**
* Startups / SMBs / Small-Medium scale projects - **Medium Networks**
* Enterprises / Large Scale projects - **Large Networks**

For more information and guidance for choosing specific orderer and peer size and number, refer to [Nodes: Peer, Orderer & CA](/products-overview/private-network/networks/nodes-peer-orderer-and-ca.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spydra.app/products-overview/private-network/networks/network-configurations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.