Skip to content

Commit cbe0c32

Browse files
committed
Suggested changes to PR #35
1 parent eabd6ad commit cbe0c32

File tree

1 file changed

+12
-6
lines changed

1 file changed

+12
-6
lines changed

content/nim/fundamentals/tech-specs.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,6 @@ You can deploy NGINX Instance Manager in the following environments:
2727

2828
{{< include "nim/tech-specs/supported-nginx-versions.md" >}}
2929

30-
## Sizing recommendations for License and Usage Reporting Only {#reporting-sizing}
31-
32-
This page assumes NGINX instances are being “managed” by NGINX Instance Manager. The sizing requirements are significantly less if you are just using NGINX Instance Manager for licensing and usage reporting only. NGINX commercial license and usage reporting is done in an “unmanaged” way, where NGINX simply sends a request periodically to NGINX Instance Manager for counting purposes. See the [Report Usage](https://docs.nginx.com/nginx-instance-manager/disconnected/report-usage-disconnected-deployment/) guide.
33-
34-
Therefore, the requirements for NGINX Instance Manager when it is just used for licensing and usage reporting is minimal (2 CPU, 4gb memory, 20gb storage).
35-
3630
## Sizing recommendations for Managing NGINX Instances {#system-sizing}
3731

3832
The following recommendations provide the minimum guidelines for NGINX Instance Manager. These guidelines ensure adequate performance, but for optimal results, we strongly recommend using solid-state drives (SSDs) for storage.
@@ -64,6 +58,18 @@ For environments requiring more resources, **large configurations** are suitable
6458
| 250 | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB |
6559
{{</bootstrap-table>}}
6660

61+
### License and usage reporting only {#reporting-sizing}
62+
63+
This section assumes you've configured NGINX Instance Manager to manage your NGINX instances for licensing and usage reporting only. NGINX commercial license and usage reporting is done in an “unmanaged” way, where NGINX sends a request periodically to NGINX Instance Manager solely for counting purposes. For more information, see how you would [Prepare your environment for reporting]({{< relref "/solutions/about-subscription-licenses.md#set-up-environment" >}}).
64+
65+
Therefore, the requirements for NGINX Instance Manager when used solely for licensing and usage reporting are minimal.
66+
67+
{{<bootstrap-table "table table-striped table-bordered">}}
68+
| Number of Data Plane Instances | CPU | Memory | Network | Storage |
69+
|--------------------------------|--------|----------|-----------|---------|
70+
| n/a | 2 vCPU | 4 GB RAM | 1 GbE NIC | 20 GB |
71+
{{</bootstrap-table>}}
72+
6773
### Sizing benchmarks for storage
6874

6975
The following benchmarks focus on **disk storage** requirements for NGINX Instance Manager. Storage needs depend on the **number of instances** and **data retention periods** (in days). The benchmarks are divided into three configuration sizes:

0 commit comments

Comments
 (0)