4 ms·
You will never massage and cram all the remote cruft efficiently enough to get back the responsiveness of an Apple II. Today’s software is turtles all the way d
by RemarkableMan 8y ago
You will never massage and cram all the remote cruft efficiently enough to get back the responsiveness of an Apple II. Today’s software is turtles all the way down from the library to the sub-library to the JIT to the application and OS and hardware and they each need 5-25 milliseconds to even wake up. That’s before you even hit the network.
Things don’t get bad, they get worse.
- majewsky 8y ago> Today’s software is turtles all the way down from the library to the sub-library to the JIT to the application and OS and hardware and they each need 5-25 milliseconds to even wake up. Where do you get these numbers? I have programs that run from start to finish in 5 ms, including tons of OS syscalls. I think many of us forgot how efficient OSes are because of the shitshow that app developers put on top.
- zimpenfish 8y agoI have a Go program that parses command line arguments, loads and parses a text file, then interprets that code on a faux-CPU. Total time 24ms start to finish for 107 faux-CPU steps (sorting 12 numbers of bunches of 3) according to `time`.
- majewsky 8y agoMine is also a Go program that reads several files and does some basic computations on top of it. I wrote about the `time` measurements here: https://blog.bethselamin.de/posts/latency-matters.html https://blog.bethselamin.de/posts/latency-matters.html