high performance static file server in Luvit

[Jak Sprats]

Hi Group,

I have experimented w/ creating very fast static webservers before,
and I think Luvit is a perfect fit for the next generation.

The trick to getting static webservers to go fast is to bypass the OS.
Caching any files that MAY be served in memory in RAM and also
gzipping them before they are served can yield that nice 50K TPS
number Tim got on his 3.4 GHz single core (depending of course on file
size {i.e. response size}).

Then an API has to be created to update files in the webserver's
cache. Anyone got any advice on how this API should look/work in
Luvit?

If a loadbalancer is in front of the static webserver, it is trivial
to taskset single webserver's to different cpu cores, have each
webserver listen on a different port and given the right NIC (and IRQ
settings) you can serve maybe 500K TPS per box. (NOTE: you need lots
of RAM, and the aggregate sum of the files you MAY serve has to be
smaller than said RAM -> but this is almost always the case).

I think a setup like this would showcase Luvit's strengths and could
be blogged about.

And then the really cool thing is, adding in dynamic logic (i.e.
control lists, or whatever) is already there, because this is a
dynamic webserver.

- jak

[Vladimir Dronnikov]

Hi!

Try tweaking my https://github.com/dvv/luvit-static

--Vladimir

[Jak Sprats]

Hi Vladimir,

looks pretty good, it has Etags, Chunks, etc...

thanks,
jak

On Mar 22, 1:56 pm, Vladimir Dronnikov <dronni...@gmail.com> wrote:
> Hi!
>
> Try tweaking myhttps://github.com/dvv/luvit-static

[Vladimir Dronnikov]

>
> looks pretty good, it has Etags, Chunks, etc...
>

Yeah. We use it at livit.io ( try stress-testing it :)