Repository navigation
Reading speed from service worker #45
Description
Activity
@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.@stefanspirkl I double checked this case and found an interesting observation
Before visiting the predicted page, I removed
avatar2.pngfrom 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.
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 😉
Upon preliminary analysis, reading speed of the service worker in sirko-io seems comparable to network. Low latency, but also low reading speed.
Data:
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?