From 68456087b8097e3975bd3836814a800c1c7b31d2 Mon Sep 17 00:00:00 2001 From: Demian Delwig Date: Mon, 30 Sep 2024 12:13:02 +0200 Subject: [PATCH] Remove line This limit is set at 30 workers per IP --- .../php/what-limits-apply-to-active-php-requests-per-ip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hypernode-platform/php/what-limits-apply-to-active-php-requests-per-ip.md b/docs/hypernode-platform/php/what-limits-apply-to-active-php-requests-per-ip.md index 7b8bdb54..9253ebca 100644 --- a/docs/hypernode-platform/php/what-limits-apply-to-active-php-requests-per-ip.md +++ b/docs/hypernode-platform/php/what-limits-apply-to-active-php-requests-per-ip.md @@ -14,7 +14,7 @@ redirect_from: Hypernodes uses Nginx and PHP-FPM for processing and serving PHP pages. PHP-FPM uses FPM worker threads to process requests from Nginx. The amount of workers that are available on the Hypernode depends on how many available CPU cores the server has. Benchmark tests have concluded that, based on CPU contention and concurrency, the optimal number of workers is defined by the formula `vCPUs * 5`. -When one IP uses up most or all of the available workers, this causes a processing queue and long loading times for PHP generated pages, possibly resulting in error codes being served to visitors. To prevent this from happening, we limit the amount of workers one IP can use. This limit is set at **30 workers per IP**. +When one IP uses up most or all of the available workers, this causes a processing queue and long loading times for PHP generated pages, possibly resulting in error codes being served to visitors. To prevent this from happening, we limit the amount of workers one IP can use. ## 30 workers per IP