Skip to content

Commit 54b0c83

Browse files
nit
1 parent fc8583a commit 54b0c83

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ layout: "learningpathall"
99

1010
Performance tuning is most useful when you treat it as a measurement process, not a fixed checklist. You can tune by changing one parameter at a time, or by running a designed experiment. You can compare profiles, or use automation and AI-assisted tools to explore a larger configuration space.
1111

12-
There isn't a universal set of tuning parameters that works best for every application. The right settings depend on the request profile, response size, TLS configuration, and cache behavior. Upstream service behavior, network path, software version, system architecture, operating system, and other application-specific factors can also affect performance.
12+
There isn't a universal set of tuning parameters that works best for every application. The right settings depend on factors such as the request profile, response size, TLS configuration, and cache behavior. Upstream service behavior, network path, software version, system architecture, operating system, and other application-specific factors can also affect performance.
1313

1414
Whatever method you use, keep the measurements repeatable. Record the system configuration, workload, software versions, and tuning parameters so you can identify which changes improved performance and which changes had little effect.
1515

0 commit comments

Comments
 (0)