No, you don't save "real time." People aren't clicking as many links as they possibly can. People read things. People browse. You don't save any actual real t

No, you don't save "real time." People aren't clicking as many links as they possibly can. People read things. People browse. You don't save any actual real time on the order of minimizing 2 milliseconds. Even if you're a large provider, you save more time doing other things than responding to HTTP requests on the order of 2 milliseconds because there are other things to do. What you are talking about is literal noise. 2 milliseconds on the web doesn't mean anything. On the web, meaningful request/response times are within one to two or more orders of magnitude larger. 2 milliseconds in simulation time means you might be doing something notably more expensive. When a single req/res time is 2 seconds long, you can think to yourself "something is wrong." When it's 200ms, you can think to yourself "something is slow." When it's 20ms, you're within the order of magnitude of a display refresh time. When you're talking about 2ms, you're talking about the amount of time that it takes to read 2 MB from an SSD. You seriously need to brush up on your understanding of latency. Try Googling "latency numbers."