From eabd6ad74623611dcde3a39ed4a66aeb33963a10 Mon Sep 17 00:00:00 2001 From: Micheal Kingston <44472403+mkingst@users.noreply.github.com> Date: Thu, 2 Jan 2025 15:20:57 +0000 Subject: [PATCH 1/2] Update tech-specs.md --- content/nim/fundamentals/tech-specs.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/nim/fundamentals/tech-specs.md b/content/nim/fundamentals/tech-specs.md index f695f5a1c..27c2125e0 100644 --- a/content/nim/fundamentals/tech-specs.md +++ b/content/nim/fundamentals/tech-specs.md @@ -27,7 +27,13 @@ You can deploy NGINX Instance Manager in the following environments: {{< include "nim/tech-specs/supported-nginx-versions.md" >}} -## Sizing recommendations {#system-sizing} +## Sizing recommendations for License and Usage Reporting Only {#reporting-sizing} + +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. + +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). + +## Sizing recommendations for Managing NGINX Instances {#system-sizing} 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. From cbe0c323e7b8e636b6bd0cf929934b611be62e9d Mon Sep 17 00:00:00 2001 From: Mike Jang <3287976+mjang@users.noreply.github.com> Date: Thu, 2 Jan 2025 08:49:45 -0800 Subject: [PATCH 2/2] Suggested changes to PR #35 --- content/nim/fundamentals/tech-specs.md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/content/nim/fundamentals/tech-specs.md b/content/nim/fundamentals/tech-specs.md index 27c2125e0..3db28325b 100644 --- a/content/nim/fundamentals/tech-specs.md +++ b/content/nim/fundamentals/tech-specs.md @@ -27,12 +27,6 @@ You can deploy NGINX Instance Manager in the following environments: {{< include "nim/tech-specs/supported-nginx-versions.md" >}} -## Sizing recommendations for License and Usage Reporting Only {#reporting-sizing} - -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. - -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). - ## Sizing recommendations for Managing NGINX Instances {#system-sizing} 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 | 250 | 4 vCPU | 8 GB RAM | 1 GbE NIC | 2 TB | {{}} +### License and usage reporting only {#reporting-sizing} + +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" >}}). + +Therefore, the requirements for NGINX Instance Manager when used solely for licensing and usage reporting are minimal. + +{{}} +| Number of Data Plane Instances | CPU | Memory | Network | Storage | +|--------------------------------|--------|----------|-----------|---------| +| n/a | 2 vCPU | 4 GB RAM | 1 GbE NIC | 20 GB | +{{}} + ### Sizing benchmarks for storage 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: