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

Higher speeds from 2.0 vs. 1.0 #860

Open
laiyi-ohlsen opened this issue Apr 6, 2020 · 5 comments
Open

Higher speeds from 2.0 vs. 1.0 #860

laiyi-ohlsen opened this issue Apr 6, 2020 · 5 comments
Assignees

Comments

@laiyi-ohlsen
Copy link

User reported issue:

For Platform 2.0, the upload speeds are slightly higher, but only by about 10-15%, and they immediately plateau again. Note that on the two charts, the Y axis is different!

Note that my download speeds are slightly higher than the M-Lab viz on the Web — the viz shows 17.4 at the first of November 2019. I had about 22.5 for the month of October 2019. The difference may be that I use the maximum speed test per day per client which would likely lead to a more optimistic number.

Screen Shot 2020-04-05 at 7 40 01 PM
Screen Shot 2020-04-05 at 7 41 04 PM
Screen Shot 2020-04-05 at 8 29 04 PM

@autolabel autolabel bot added the review/triage Team should review and assign priority label Apr 6, 2020
@autolabel autolabel bot added 2020 Week 15 and removed review/triage Team should review and assign priority labels Apr 6, 2020
@mlab-code-reviews
Copy link

mlab-code-reviews commented Apr 6, 2020 via email

@BobBallance
Copy link

I typically take the median across the clients, and the max per day within the client. You can see the mean across clients, but that's not the recommended view within I3.

@mlab-code-reviews
Copy link

mlab-code-reviews commented Apr 6, 2020 via email

@gfr10598
Copy link
Contributor

This probably belongs in another repo. etl just does the parsing, and this is more associated with either the server or the platform or both.

@mattmathis
Copy link
Contributor

At least one problem is in the parser/views, and legacy issues in the platform itself are not actionable.

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

No branches or pull requests

5 participants