-
Notifications
You must be signed in to change notification settings - Fork 73
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
Distributor Node Quality Checks - 1 #744
Comments
As per @traumschule this is covered by #679. Moving to "In Review" |
Covered would mean fully implemented. The code can be reused but does not have the purpose to simulate atlas user experience with puppeteer. It performs |
@freakstatic any updated on the internal review? |
sorry for the late reply, I was able to run it and got this file as output. |
so I suggest that we develop something with puppeteer if the objective is to check how good are the distributors when using atlas. |
Ok, clear. Moving back to |
|
Bounty link - https://dao.joystream.org/#/bounty/preview/68 |
Bounty submission failed the internal review, sent back to the worker and got stuck. Moving back to ToDo. Please consider this vacant and ready to be picked up. |
excited to join! |
Assigned to @m00n620 |
Worker asked to un-assign this piece of work. |
Workflow
Dev points: 15
JSG Reviewer: @DzhideX
Notes
PR to be made to this repo
Feel free to ask questions, but ask them publicly in the issue, and ping me on discord
bwhm#6514
so I'll see it :)Scope
Measuring the quality of service by the Distributors without proper tools is a very manual (and error prone) job.
First, we create a tool that fetches thumbnails from the front page. The tool has to be somewhat customizable, as in reality, users don't need to get every single asset at the same time.
Scope 1
Use puppeteer, or a similar free and open source tool, to create a script that mimics a user opening play.joystream.org and other sub-pages without caching locally.
Each time the script runs, it logs:
Then, get the latency to each distributor, and get some data from the query-node to determine:
To avoid unfair rulings:
The text was updated successfully, but these errors were encountered: