[agentgt]

> Elyxel was designed and built with performance in mind. Styles and any additional flourishes were kept to a minimum. My choice of Elixir & Phoenix was driven by this consideration as well. Most of the pages are well under 100 kilobytes and load in less than 100 milliseconds5. I find it's always helpful to keep performance in the back of your mind when building something.

Thats much appreciated but I was kind of hoping you (the author) would go into more details about request time. Most people can (and should) do the above. However I would be more interested in what Elixer + CRUD is like particularly for TTFB. Like does the author do streaming (I don't necessarily mean websockets or comet)?

After all if the TTFB is really slow the CSS optimizations and what not matter little.

In traditional request per thread (or whatever is analagous) web framework paradigms the request is a single thread and often waits for the database to finish before moving on to display the page. I would imagine Elixir has a better answer at least for read only pages.

[pdimitar]

On my virtual Debian, the development version of a relatively complex website -- which is probably anywhere between 5 to 30 times slower than production -- has 450ms for the first ever request after the server starts. Anything from then on goes between 0.2 to 12ms.

Not really telling you much, I know, but these are pretty standard numbers for Elixir + Phoenix apps.

[abrookewood]

Time To First Byte?