Received: by 10.236.175.196 with SMTP id z44mr17626257yhl.6.1332512595345;
        Fri, 23 Mar 2012 07:23:15 -0700 (PDT)
X-BeenThere: luvit@googlegroups.com
Received: by 10.236.140.106 with SMTP id d70ls6046912yhj.6.gmail; Fri, 23 Mar
 2012 07:23:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.176.6 with SMTP id a6mr2568792yhm.12.1332512595083; Fri,
 23 Mar 2012 07:23:15 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
 jakspr...@gmail.com designates internal as permitted sender)
 smtp.mail=jakspr...@gmail.com; dkim=pass
 header...@gmail.com
Received: by em9g2000vbb.googlegroups.com with HTTP; Fri, 23 Mar 2012 07:23:14
 -0700 (PDT)
Date: Fri, 23 Mar 2012 07:23:14 -0700 (PDT)
In-Reply-To: <CAE9na_NsgVfKBrA3uyUQV5ryqECpyXM94+GcBbdP4CipQsfXbA@mail.gmail.com>
References: <358408db-d885-41da-87a6-2766aa37307d@q11g2000vbu.googlegroups.com>
 <CAE9na_NsgVfKBrA3uyUQV5ryqECpyXM94+GcBbdP4CipQsfXbA@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
 AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7,gzip(gfe)
Message-ID: <f66642fc-68e0-4245-be2c-20d638539ced@em9g2000vbb.googlegroups.com>
Subject: Re: high performance static file server in Luvit
From: Jak Sprats <jakspr...@gmail.com>
To: luvit <luvit@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Vladimir,

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

thanks,
 jak

On Mar 22, 1:56=A0pm, Vladimir Dronnikov <dronni...@gmail.com> wrote:
> Hi!
>
> Try tweaking myhttps://github.com/dvv/luvit-static
>
> --Vladimir
>
>
>
>
>
>
>
> On Thu, Mar 22, 2012 at 12:03 PM, Jak Sprats <jakspr...@gmail.com> wrote:
> > 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.
>