3 ms·
> We're working on applications that's either waiting for the disk, waiting for the db, waiting for some http server or waiting for the user. If you try to be
by anonymoushn 4y ago
> We're working on applications that's either waiting for the disk, waiting for the db, waiting for some http server or waiting for the user.
If you try to be good at waiting on many things, you can use one machine instead of a hundred
> None of our customers will notice the difference if my button click event handler takes 50ms instead of 10ms
They absolutely will, what
- magicalhippo 4y ago> If you try to be good at waiting on many things, you can use one machine instead of a hundred We can't run on one, because customers run our application on-prem. > They absolutely will, what How can you be so sure?
- anonymoushn 4y agoHave you tested this? 40ms of additional interaction delay is extremely noticeable.
- magicalhippo 4y agoYou're missing the point. Sure, 10ms vs 40ms is measurable, and for the keen-eyed noticeable. But if you're only pressing the button once every 5 minutes, it doesn't matter. Similarly, if the button triggers an asynchronous call to a third-party webservice that takes seconds to respond, it doesn't matter. And so on. Of course, for the things where users are affected by low latency, we try to take care. But overall that's a very, very small portion out of our full functionality.