Measure the time an async I/O event has spent in the io_service completion event queue
up vote
0
down vote
favorite
I am wondering if there is a way to measure the time an async I/O event such as async_read or async_write spent in the io_service completion event queue before its completion handler got called.
The problem here is that you can't really timestamp the time when the event was inserted in the io_service queue which is something you can do when you post work to the io_service yourself - boost::asio::io_service occupied queue lengths for timers and posts
The idea is to check if an event has stayed in a ready state for too long. Then, you can eventually react on this and dynamically increase the worker threads.
boost io boost-asio asio
add a comment |
up vote
0
down vote
favorite
I am wondering if there is a way to measure the time an async I/O event such as async_read or async_write spent in the io_service completion event queue before its completion handler got called.
The problem here is that you can't really timestamp the time when the event was inserted in the io_service queue which is something you can do when you post work to the io_service yourself - boost::asio::io_service occupied queue lengths for timers and posts
The idea is to check if an event has stayed in a ready state for too long. Then, you can eventually react on this and dynamically increase the worker threads.
boost io boost-asio asio
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am wondering if there is a way to measure the time an async I/O event such as async_read or async_write spent in the io_service completion event queue before its completion handler got called.
The problem here is that you can't really timestamp the time when the event was inserted in the io_service queue which is something you can do when you post work to the io_service yourself - boost::asio::io_service occupied queue lengths for timers and posts
The idea is to check if an event has stayed in a ready state for too long. Then, you can eventually react on this and dynamically increase the worker threads.
boost io boost-asio asio
I am wondering if there is a way to measure the time an async I/O event such as async_read or async_write spent in the io_service completion event queue before its completion handler got called.
The problem here is that you can't really timestamp the time when the event was inserted in the io_service queue which is something you can do when you post work to the io_service yourself - boost::asio::io_service occupied queue lengths for timers and posts
The idea is to check if an event has stayed in a ready state for too long. Then, you can eventually react on this and dynamically increase the worker threads.
boost io boost-asio asio
boost io boost-asio asio
edited 8 hours ago
asked 9 hours ago
ladaManiak
89116
89116
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371774%2fmeasure-the-time-an-async-i-o-event-has-spent-in-the-io-service-completion-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown