Skip to content

Commit eabd6ad

Browse files
authored
Update tech-specs.md
1 parent bb82176 commit eabd6ad

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

content/nim/fundamentals/tech-specs.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,13 @@ You can deploy NGINX Instance Manager in the following environments:
2727

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

30-
## Sizing recommendations {#system-sizing}
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+
## Sizing recommendations for Managing NGINX Instances {#system-sizing}
3137

3238
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.
3339

0 commit comments

Comments
 (0)