Re: [asio] monitoring io_context load
Dmitry via Boost-users <[email protected]> Fri, 30 Jun 2023 17:31:09 +0300
| Newsgroups | gmane.comp.lib.boost.user |
|---|---|
| Message-ID | <CA+POfmt19ysr+R2hgr16_OPBckk8Gjs9wm4QA054H83QL0Gmyw@mail.gmail.com> |
Thanks! We already have a similar metric. The problem is that measured latency grows only after io_context becomes overloaded: when the queue grows because all threads are busy. I would like to measure io_context load before it became overloaded to estimate capacity. Thanks, Dmitry On Fri, Jun 30, 2023 at 17:00, Vinnie Falco via Boost-users < [email protected]>: > On Fri, Jun 30, 2023 at 6:58 AM Dmitry via Boost-users > <[email protected]> wrote: > > I would like to have a metric that measures time spent for > > work (executing completion handlers) vs time spent waiting > > for work in thread pool executing io_context::run(). > > Maybe there are some ideas here? > > > https://github.com/XRPLF/rippled/blob/f18c6dfea7870132490124e1942901a6a0cddc7e/src/ripple/beast/asio/io_latency_probe.h#L34 > > Thanks > _______________________________________________ > Boost-users mailing list > [email protected] > https://lists.boost.org/mailman/listinfo.cgi/boost-users > _______________________________________________ Boost-users mailing list [email protected] https://lists.boost.org/mailman/listinfo.cgi/boost-users