ecyrb wrote>
Server overload does not come from network overload, but from service overload. If you can't serve (compute) more requests/s than the network load, your server is overloaded... You can compute your server overload by queuing requests. If your queue becomes too big, you can consider that your server is under heavy pressure and take appropriate measures to circumvent the flow of requests (load balancing etc...)
Is there any asio example in the docs, which demostrate this Does the io_service expose the queue of request/connections as I have not seen such an api ? or do you mean that server should be structured to maintain its _own_ queue.( as apposed to the queue in io_service) Request are then handled from this internal queue? Best regards, Ta, Avi