A functional-first toolkit for building brilliant #aspnetcore applications using #fsharp on #dotnet
Blistering fast, memory efficient, AOT compliant and more
Thank you to all of those who have reported broken links on the docs site. And submitted PRs. Truly appreciated.
The reason I haven't merged any of these is because I have been feverishly working away at a content refresh, which will eliminate them naturally.
Docs have been updated to include some additional detail surrounding host configuration and deployment methodologies.
https://t.co/pBe1IlltfY
https://t.co/dM0e8JyvMX
Thanks to @Aaronontheweb for getting the discussion started, @stuartbright and @ChetHusk for the assist.
Since Falco is free of reflection and dynamic code, it natively supports trimming and AoT. Yielding surprisingly small and efficient single file binaries ๐งโโ๏ธ
If you're running within a scale to zero environment, don't forget about the ready to run flag โ ๏ธ
#3, Go had the lowest initial footprint, but consumed most CPU and RAM under load.
#2, Razor Slices had the highest initial footprint, but consumed only modest CPU and RAM under load.
#1, Falco was the best blend of initial footprint, and resource consumption under load.
The reason Falco can out perf these other lightweight templating packages is that it completely eliminates the most costly part of templating, parsing.
I am so impressed by Razor Slices, I didn't know it was possible to achieve those perf characteristics using Razor.
I pitted it against: Falco (naturally) and Go.
I was very shocked by the results.
Source:
https://t.co/9GI8yZwEdQ