You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/nim/fundamentals/tech-specs.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,12 +27,6 @@ You can deploy NGINX Instance Manager in the following environments:
27
27
28
28
{{< include "nim/tech-specs/supported-nginx-versions.md" >}}
29
29
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
-
36
30
## Sizing recommendations for Managing NGINX Instances {#system-sizing}
37
31
38
32
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
64
58
| 250 | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB |
65
59
{{</bootstrap-table>}}
66
60
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.
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