-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ASIO latency] io_latency_ms measure does not update #2521
Comments
Hmm! Thanks for this. Will look into this. |
hi @mellery451 ! |
seelabs
pushed a commit
to seelabs/rippled
that referenced
this issue
Jun 1, 2018
Fixes: XRPLF#2521 Copy ctor missed one member. Also added move since we have some rvalues passed around here.
seelabs
pushed a commit
to seelabs/rippled
that referenced
this issue
Jun 1, 2018
Fixes: XRPLF#2521 Copy ctor missed one member. Also added move since we have some rvalues passed around here.
seelabs
pushed a commit
to seelabs/rippled
that referenced
this issue
Jun 1, 2018
Fixes: XRPLF#2521 Copy ctor missed one member. Also added move since we have some rvalues passed around here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
Recently I've found that
io_latency_ms
reported byserver_state
is last read value ofApplicationImp::m_io_latency_sampler
. However it looks like measure which is started on Application startup stalls after few successful measures and never updates again.(I added log in callback to
template <class Duration> void operator() (Duration const& elapsed)
and it only executes for like... 2-5 seconds after startup
Its pretty easy to observe/reproduce but its hard for me to determine why it stalls...
for instance
tc qdisc add dev eth0 root netem delay 11ms
tc qdisc del dev eth0 root netem
The text was updated successfully, but these errors were encountered: