1. 15

  2. 4

    TLDR; no. Yet this little pure Ruby webserver is surprisingly capable. While it doesn’t best NGINX it does put up one heck of a fight.

    1. 2

      there’s essentially no human discernible difference between a 30ms and 10ms response time.

      For 1 html file no… but for a whole website with 50 assets, yes it does.

      1. 3

        30 ms is perc 95 which means 95% of all requests will be that speed or faster. So if you’re loading 50 assets the average of them would be 7ms.

        If you’re serving that many assets you should also be using a CDN and doing things like async loading of JavaScript. Also you should be using CSS concatenation library like Sprockets (same with JS) so you’re only looking at 2 assets plus images & 48 images on one page is a LOT.

        Even if you’re not using a CDN in the worst case the HTML would be 30ms and the CSS would be 30 ms and then the page would start to render. This is under 100ms and would seem “instantaneous”. The JS loaded with async tag and images may be delayed in loading but the page is still useable and readable.

        1. 2

          Thank you very much for your reply! That makes sense indeed!