3 ms·
These results are valid if your static content all fit in memory. I would expect interesting diversions in performance if a certain proportion of requests would
by mseebach 15y ago
These results are valid if your static content all fit in memory. I would expect interesting diversions in performance if a certain proportion of requests would have to hit the file system.
Also an interesting piece of noise missing is slow clients holding on to the connection. If you're serving up multi-megabyte files, I would guess this could become a major factor.
- peterwwillis 15y agopart of why you use caching servers or proxies is to avoid hitting the filesystem, since it's very costly compared to memory (or even network to an extent). the ramdisk in this case is performing the function of the caching server but at much increased speed and much reduced overhead. afaik the only way you could get over a couple thousand RPS while reading from the filesystem is due to inherent caching of the VFS and disk buffers by the operating system. and in an asynchronous web server, connections should not be held up by slow clients. if they use a model where one thread or process handles each client connection you could definitely get starvation of resources or connections, but asynchronous models should just process stuff as it comes in and not "wait" on a slow client.