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.

Sign up for GitHub

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

Jump to bottom

Blobber monitoring #1714

Open

Jayashsatolia403 opened this issue Dec 23, 2024 · 0 comments

Assignees

Collaborator

Jayashsatolia403 commented Dec 23, 2024 •

edited

Loading

we need a performance measurement code in the gosdk

for every block upload/download we need to register the time spent for each blobber, some simple message <blobber_id, alloc_id, time_spent>
all this messages we need to push to a channel, no-op by default.
wasm can collect this messages in background task analyze and decide which blobber is bad

also we will use exactly same mechanics for global monitoring tool (alloc crawler)

we will create different allocations on different blobbers, keeping all pairs in pool
crawler will continuously take pairs from the pool and make upload/download generating the same messages with gosdk
timings can be stored to any local db, later crawler can build statistics and ranks for all the blobbers based on it

https://0chain.slack.com/archives/G01EXH6EYC9/p1734969371661059

Jayashsatolia403 self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment