I have an SSD but that doesn't matter. The file is fully cached but the CPU cost of 114,801 tiny reads is non-trivial. Reading the file in one read from Python takes a few ms.
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
https://randomascii.wordpress.com/2019/09/08/taskbar-latency-and-kernel-calls/ … I mostly just wanted to see how long it would take me to write a post from scratch. Twitter says one hour. I think it was a bit longer. Any typos are because my editor is already asleep.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
From one point of view, 7us per file read is pretty impressive…
-
It helps that it ultimately just does a 68 byte memcpy (on average), at which point 7μs doesn't seem quite as good :-(
Kraj razgovora
Novi razgovor -
-
-
I'm not trying to play a devil's advocate here but there's a lot of under-the-hood activity that's going on when you RMB on a file: system registry scooping, comms via COM with various COM servers, etc. Can only imagine Explorer is a huge project and it's not that trivial to..
-
Sure, systems are complicated and mistakes happen. In this case CAutomaticDestinationList::GetDataInternal is significantly broken, from a performance perspective, and needs fixing. I think Microsoft will do that now that they realize that it consumes an easily avoidable 500+ ms.
Kraj razgovora
Novi razgovor -
-
-
File explorer or internet explorer? How about edge?
-
This is File Explorer. See the blog post for full details.https://randomascii.wordpress.com/2019/09/08/taskbar-latency-and-kernel-calls/ …
Kraj razgovora
Novi razgovor -
-
-
Not that it makes it any better, but is it registry access?
-
Nope, it's 114,801 reads from one file, average read size of 68 bytes. These are calls to ReadFile - kernel calls - with no CRT buffering to avoid them.https://randomascii.wordpress.com/2019/09/08/taskbar-latency-and-kernel-calls/ …
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.