Skip to content
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

Big slowdown on processing historical messages on reconnections #812

Closed
matiwinnetou opened this issue Apr 5, 2023 · 4 comments
Closed
Assignees
Labels
bug 🐛 Something isn't working

Comments

@matiwinnetou
Copy link
Contributor

Hydra version: 0.9.0

We processed about 500 various messages, among transactions, a few SnapshotConfirms where UTxOs list was never longer than 1000 in size.

What we observe is that when websocket client disconnected and reconnected, the pattern is always the same. First there is nothing for 10, 20, 30 seconds (haven't exactly messured). CPU goes 100% for hydra node and then there is a BURST of all messages over websocket in one go.

This is now what we are expecting, when processing historical messages we expect messages to be gradually piped and without significant delay at the start.

@matiwinnetou matiwinnetou added the bug 🐛 Something isn't working label Apr 5, 2023
@v0d1ch
Copy link
Contributor

v0d1ch commented Apr 6, 2023

Hey @matiwinnetou 👋
Thanks for reporting this to us.

Do you have a way of reproducing this issue consistently and if so can you send us your local state and/or some instructions so we have easier time observing this issue on our end?

@matiwinnetou
Copy link
Contributor Author

I think so, we can do some zoom session next week I think. I am using postman for validation so I also need to check with another client because could be postman issue as well.

@v0d1ch
Copy link
Contributor

v0d1ch commented May 9, 2023

Hey @matiwinnetou any related news on this?

@v0d1ch
Copy link
Contributor

v0d1ch commented Jun 30, 2023

@matiwinnetou can we close this issue or do you still think there is a problem?

@v0d1ch v0d1ch closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants