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

Load shedding for event service #89

Open
dcadenas opened this issue May 21, 2024 · 4 comments
Open

Load shedding for event service #89

dcadenas opened this issue May 21, 2024 · 4 comments
Assignees

Comments

@dcadenas
Copy link
Contributor

A load shedding strategy when we are under backpressure instead of full disconnection as we currently do. Currently when we reconnect we grab 1 hour of data from each relay and that's very hard to change and integrate with the backpressure signal from the consumer. Load shedding is easier to skip that hour surge of events on reconnects and also opens the door to future more dynamic/intelligent adaptations under load.

Screenshot 2024-05-20 at 1 32 08 PM
@dcadenas dcadenas self-assigned this May 21, 2024
@dcadenas
Copy link
Contributor Author

dcadenas commented May 21, 2024

I already merged a PR for this. Now just checking because I think the speed of processing events used to be faster

@dcadenas
Copy link
Contributor Author

I suspect that the surge that made me do this change was related to a surge in profiles (see https://stats.nostr.band/#relay_users):

Image

@dcadenas
Copy link
Contributor Author

@dcadenas
Copy link
Contributor Author

This is working but I'm letting it run for a while to see metrics before closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: QA
Development

No branches or pull requests

1 participant