From 7216c39bc5bb4b7ecb723f5473f50812a978cc54 Mon Sep 17 00:00:00 2001 From: Michael Vernik Date: Wed, 26 Feb 2025 14:11:51 -0800 Subject: [PATCH] class8: updates addressing feedback from appworld day 1 --- docs/class8/module3/module3.rst | 4 ++++ docs/class8/module4/module4.rst | 3 --- docs/class8/module5/module5.rst | 4 +++- 3 files changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/class8/module3/module3.rst b/docs/class8/module3/module3.rst index b1a30f99..e1fba1c6 100644 --- a/docs/class8/module3/module3.rst +++ b/docs/class8/module3/module3.rst @@ -39,6 +39,10 @@ Increase rlimit to 4096, by uncommenting line 4 * worker_rlimit_nofile 4096; +Increase worker_connections from 1024 to 4096 + +* worker_connections 4096; (line 11 or 12) + Publish the new configuration. .. image:: /class8/images/nim-rlimit-4096.png diff --git a/docs/class8/module4/module4.rst b/docs/class8/module4/module4.rst index 176b97cf..5f311afe 100644 --- a/docs/class8/module4/module4.rst +++ b/docs/class8/module4/module4.rst @@ -67,9 +67,6 @@ Host: http://10.1.1.9/ Advanced Options, Run time: 30s -.. image:: /class8/images/locus-500-50-30.png - :width: 200 px - .. note:: Where you do see the performance improvement in the Locust chart? .. note:: Review NGINX Dashboard cache section. How much bandwidth was saved from going to upstream server? (For a hint, refer to the HINTS section at the bottom of this page.) diff --git a/docs/class8/module5/module5.rst b/docs/class8/module5/module5.rst index 0b0da994..914db8cc 100644 --- a/docs/class8/module5/module5.rst +++ b/docs/class8/module5/module5.rst @@ -64,7 +64,9 @@ Review the following lines in the nginx.conf file. Uncommenting these directives * `limit_conn_zone $binary_remote_addr zone=addr:10m;` * `limit_conn addr 400;` -.. note:: Both connection and rate limits are advised as best-practices for any service running in production. These parameters can help defend against some Denial-of-Service attacks, as well as, prevent back-end application servers from being overwhelmed with rouge traffic. +Both connection and rate limits are advised as best-practices for any service running in production. These parameters can help defend against some Denial-of-Service attacks, as well as, prevent back-end application servers from being overwhelmed with rouge traffic. + +.. note:: If you attempted to enable both connection and request limiting did you notice any errors when publishing the update? What could be a good solution to this? Ask for help if you need any assistance. 6. **Review upstream keepalive parameters**