3 ms·
> 5 billion cycles per second IF everything is in the cache, there is no dependency on I/O, and cycles aren't wasted with context switching between usermode->k
by tenebrisalietum 4y ago
> 5 billion cycles per second
IF everything is in the cache, there is no dependency on I/O, and cycles aren't wasted with context switching between usermode->kernel.
Unless your program is purely computational it's going to burn cycles on system calls and I/O.
- josephg 4y agoYour computer can do an awful lot of syscalls and IO in 1 second. And almost all of the network traffic and syscalls can be mitigated almost all of the time. Eg by caching, buffered IO, cutting out bloat, minifying javascript, static rendering, using lower res assets, and so on. There’s exceptions - AI, video games, rendering and simulations work can take real time. But other than that, modern computers should boot instantly, and apps should open instantly. Webpages should open within about 3x the server round trip time. There is very little software I’ve ever worked with that, with some effort, couldn’t be massively optimized.