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

Reading speed from service worker #45

Open
m0-n opened this issue Apr 10, 2019 · 3 comments
Open

Reading speed from service worker #45

m0-n opened this issue Apr 10, 2019 · 3 comments

Comments

@m0-n
Copy link

@m0-n m0-n commented Apr 10, 2019

Upon preliminary analysis, reading speed of the service worker in sirko-io seems comparable to network. Low latency, but also low reading speed.

Data:
image

Total load time demo: 1.0 - 1.5s

Is that a bug / some IO blocking in the SW ? How can that number be brought down to 20-30ms as normal read operations?

@dnesteryuk
Copy link
Collaborator

@dnesteryuk dnesteryuk commented Apr 11, 2019

@stefanspirkl I assume this image wasn't in the cache 🤔 Once the engine makes the prediction, the browser needs time to download content. If a user moves too fast between pages, there won't be enough time for downloading. Cached content can be checked in Application -> Cache storage.

@dnesteryuk
Copy link
Collaborator

@dnesteryuk dnesteryuk commented Apr 11, 2019

@stefanspirkl I double checked this case and found an interesting observation

Untitled

Before visiting the predicted page, I removed avatar2.png from the cache storage, it took only 6 ms (2 ms were spent on downloading from the disk cache) to deliver it. Meanwhile, the other images were delivered within 30 ms.

I see from your example that it took 386 ms to deliver post01.jpg. Meanwhile, 27 ms were needed to get it from the disk cache. So, what was happening other 359 ms?!

My first assumption is a restriction to a number of concurrent requests to the cache storage.

@dnesteryuk
Copy link
Collaborator

@dnesteryuk dnesteryuk commented May 31, 2019

Hi @stefanspirkl finally, I got time to investigate this issue. Here is a first result https://nesteryuk.info/2019/05/25/chrome-cache-storage-vs-disk-cache.html I will keep you updated when I find something more 😉

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

Successfully merging a pull request may close this issue.

None yet
2 participants