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
-
Show this thread
-
Loading 2kb from disk taking 80 milliseconds is one reason why web apps still feel like shitpic.twitter.com/70jP9cIyrJ
3 replies 1 retweet 6 likesShow this thread -
-
Replying to @kevinmarks
It seems like it's because the disk cache is in a separate chrome worker process, so you eat multiple process context switches to read from it
2 replies 0 retweets 0 likes -
-
Replying to @kevinmarks @antumbral
Yep. This is known-bad. Fixes went in last year for read storms, but Scheduling Is Hard (TM) /cc
@inexorabletash2 replies 0 retweets 1 like -
Replying to @slightlylate @kevinmarks and
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
1 reply 0 retweets 1 like -
Replying to @slightlylate @kevinmarks and
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.
3 replies 0 retweets 1 like -
Initial naive thought "can't you just mmap a chunk for the small ones" - then I remembered Spectre. Caching is hard.
1 reply 0 retweets 1 like
More like "sharing of all kinds is hard". Isolating origins from each other takes up most of our days.
-
-
Replying to @slightlylate @kevinmarks and
The fact that I can't give blanket perms to an iframe took up all of my days last week.
0 replies 0 retweets 1 likeThanks. 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.