Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently I´m not sure, I try to make a high-performance server, I got a 6Core CPU, so if I would use the “io_service_per_cpu” design, I have 6 io_service´s.
I already heard that the threadpool design isn´t the best one, but I´m not sure about that.
What knowledge do you have? Someone already made a Stress test with each, or something else?
In my experience it is vastly easier to approach asynchronous application design with the following order:
io_serviceio_service::run()from a singleio_service. Use strands for handlers that require access to shared data structures.io_serviceper cpuThe motivation for changing between each of these designs should be done after profiling your application. Note that the HTTP Server 2 example only shows how to use an
io_serviceper CPU, it does not show you when or why to use such a design.