The Web App Experience: I made my extension prefetch the two big/slow resources this page relies on, but it's only .5sec faster because the rest of the 2.5 secs of load time are Chrome's disk cache waddling around grabbing files off my SSD 37 bytes at a time
-
-
The architecture uses 2 reads: the first is for item location (a round-trip via the Browser Process I/O thread) and, in most cases, a second read for the actual body/data
-
Those are running through a single I/O thread, which means you can often see a pile of index reads delaying body reads. The delay is bonkers-slow.
- 10 more replies
New conversation -
-
-
It seems to do roughly the right thing for assets that are being loaded in parallel (<img> tag, etc) but it does some sequential XHRs against cache that are still pretty slow. I can manually intercept the XHRs, but I don't know how to get the cached data any faster. indexeddb?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.