adding summaries and faqs

Author: anupras-mohapatra-arm

content/learning-paths/servers-and-cloud-computing/nginx_tune/_index.md

@@ -17,9 +17,56 @@ prerequisites:
     - A repeatable HTTP workload or load test that you can run before and after tuning.
     - If you don't already have an NGINX setup, see [Learn how to deploy NGINX](/learning-paths/servers-and-cloud-computing/nginx/).
 
+# START generated_summary_faq
+generated_summary_faq:
+  template_version: summary-faq-v3
+  generated_at: '2026-06-30T15:49:37Z'
+  generator: ai
+  ai_assisted: true
+  ai_review_required: true
+  model: gpt-5
+  prompt_template: summary-faq-v3
+  source_hash: 39f9323dac9bd7f5480e501ad8fd93d2d9999c420ed1c2eb45eba2ccb3be63ad
+  summary_generated_at: '2026-06-30T15:49:37Z'
+  summary_source_hash: 39f9323dac9bd7f5480e501ad8fd93d2d9999c420ed1c2eb45eba2ccb3be63ad
+  faq_generated_at: '2026-06-30T15:49:37Z'
+  faq_source_hash: 39f9323dac9bd7f5480e501ad8fd93d2d9999c420ed1c2eb45eba2ccb3be63ad
+  summary: >-
+    You'll learn how to tune NGINX on Arm-based platforms using a measurement-first
+    workflow. First, you'll establish a baseline, then iteratively adjust Linux network stack parameters and
+    evaluate compiler and library choices such as OpenSSL, PCRE, and zlib. You'll review tuned configuration examples and guidance for sizing directives to refine configurations
+    for static file serving, reverse proxy, and API gateway scenarios. You're also introduced to `wrk`
+    as an option for generating traffic and reporting throughput and latency on NGINX. By the end, you'll use `wrk` to compare before-and-after results and verify the impact of each change.
+  faqs:
+  - question: How do I know whether a tuning change improved performance?
+    answer: >-
+      Re-run the same repeatable workload and compare throughput and latency before and after
+      the change. Adjust one parameter at a time or use a designed experiment so results are attributable
+      to specific settings.
+  - question: Where do I change Linux network parameters when tuning?
+    answer: >-
+      Modify settings in /etc/sysctl.conf or use the sysctl command. Refer to the Linux kernel
+      sysctl documentation, and treat these changes as part of the same measurement process used
+      for NGINX directives.
+  - question: Do I need to use wrk if I already have a load test?
+    answer: >-
+      No. If you already have a repeatable HTTP workload, use that. wrk is provided as a starting point
+      only when you do not already have an established test method.
+  - question: When tuning the reverse proxy or API gateway, what should I reuse from the static
+      file server configuration?
+    answer: >-
+      Use the same top-level nginx.conf from the static file server section. Then apply the tuned
+      reverse proxy and API gateway configuration and validate the result with repeatable measurements.
+  - question: How do compiler, OpenSSL, PCRE, and zlib choices factor into tuning?
+    answer: >-
+      Evaluate these choices as part of your experiments because they can affect NGINX performance.
+      Compare alternatives using the same workload and interpret results alongside your NGINX
+      and kernel changes.
+# END generated_summary_faq
+
 author: Julio Suarez
 
-generate_summary_faq: true
+generate_summary_faq: false
 rerun_summary: false
 rerun_faqs: false
 
@@ -73,3 +120,4 @@ weight: 1                       # _index.md always has weight of 1 to order corr
 layout: "learningpathall"       # All files under learning paths have this same wrapper
 learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
 ---
+