From 09a293abd8aeed11f037512d0b8da8e43fafcc68 Mon Sep 17 00:00:00 2001 From: Dushmanta Date: Thu, 20 Mar 2025 15:55:47 +0530 Subject: [PATCH] docs: remove dead links from performance tuning page --- docs/categories/06-Advanced/performance-tuning.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/categories/06-Advanced/performance-tuning.md b/docs/categories/06-Advanced/performance-tuning.md index fae85216..5880f5fd 100644 --- a/docs/categories/06-Advanced/performance-tuning.md +++ b/docs/categories/06-Advanced/performance-tuning.md @@ -100,7 +100,7 @@ After: ## At the OS level -There are lots of good articles on how to tune your OS to accept a large number of connections. Please see [this one](https://blog.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/) or [this one](https://medium.com/@elliekang/scaling-to-a-millions-websocket-concurrent-connections-at-spoon-radio-bbadd6ec1901) for example. +There are lots of good articles on how to tune your OS to accept a large number of connections. Please see [this one](https://medium.com/@elliekang/scaling-to-a-millions-websocket-concurrent-connections-at-spoon-radio-bbadd6ec1901) for example. While [load testing](load-testing.md) your Socket.IO server, you will likely reach the two following limits: @@ -149,4 +149,3 @@ Once you reboot your machine, you will now be able to happily go to 55k concurre See also: - https://unix.stackexchange.com/a/130798 -- https://making.pusher.com/ephemeral-port-exhaustion-and-how-to-avoid-it/