-
Notifications
You must be signed in to change notification settings - Fork 27
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
10-12 seconds added to trampoline payment for unknown reason #535
Comments
We are looking into instrumenting the nodes with the tracing support. That should tell us nicely where we're spending time. |
@JssDWt do you know how many channels the node has with the trampoline peer? |
The node has 1 channel with the trampoline peer. And 1 channel total. |
We have deployed the opentelemetry tracing, including DB call measurements, so next time we see an instance we can dig deeper 👍 |
I guess there is nothing more we can do here at the moment. Shall we close this issue and come back to it once there is a new incident we can work on? |
Is there an alert set for slow listpeerchannels calls? |
We are actively monitoring the duration of I plan to instrument the |
I had 2 occurrences of trampoline payments where 10-12 seconds were added in what seems to be a listpeerchannels call. You see between
overpay=4050.0000000000005, total_amt=14050
andStarting 1 tasks to wait for channels to be ready
there is a 10-12 seconds delay. In between those I only see alistpeerchannels
call in the code. No awaiting channels, no communication with the signer necessary.(Note the times here are recorded on the client side, so they may be distorted)
Node id:
02343160e016c025ba56a364c160761e709d36eb8e25630a86b363ef9a5d86f3cf
Session id: 7256626926981120
Payment 1:
Payment 2:
The text was updated successfully, but these errors were encountered: