|Just another Perl shrine|
If his central socket server script is to be able to handle 100,000 (1 lakh) concurrent "jobs"; then it will it will be critical to overall throughput that it be responsive to incoming connections/messages. Microseconds will count.
While the individual jobs may well be IO-bound,if the socket server that sits in the driving seat of all of those processes is unresponsive; then it will have a potentially disastrous affect on overall system throughput by keeping 99,999 jobs waiting --doing nothing -- whilst it deals with the current job.
All of this is plainly obvious to anyone with a modicum of analytical experience.
And even to those who bothered actually read what was actually written; rather than imagineering a scenario to fit their personal biases.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^4: how to improve the performance of a perl program