[erlang-questions] Static files served through Webmachine

[Tristan Sloughter]

Sam, Jesper both these sound great, thanks! I'm also going to look into what
Jack was saying about how Rails handles some stuff.

But I'm leaning towards Jesper's idea with Varnish being the best... I'm one
of those people who scoff at most benchmarks so not sure I'll bother to do
one for this, but maybe, if someone here can A) suggest the best setup for
it B) if it makes sense at all or would just be another worthless benchmark
that really gives no information about reality.

Thanks!
Tristan

On Tue, Jul 19, 2011 at 7:00 AM, Jesper Louis Andersen <
jesper.louis.andersen@REDACTED> wrote:

> On Tue, Jul 19, 2011 at 03:27, Tristan Sloughter
> <tristan.sloughter@REDACTED> wrote:
>
> > Can anyone think of a way I can keep the nice URLs and serve the static
> html
> > files through nginx or another webserver.
>
> Put a Varnish accelerator in front of your system
> (https://www.varnish-cache.org/). That way, it doesn't matter if your
> backend is slow at serving files as the accelerator will just cache
> static stuff for you. In addition, you avoid the trouble of going
> through another system as a proxy for static content. Also, the
> solution is quite modular. On the development system, you don't need
> more than a single system running Erlang.
>
> In my opinion, there is little reason not to plug into the whole
> industry there is where the main point is to make serving HTTP go
> faster. Trying to beat that with Erlang is probably possible, but I
> don't think it is beneficial. Varnish is really really hard to beat.
> It is built specifically for being insanely fast and it serves its
> data from a shared mmap()'ing, scales to multiple CPUs and is a big
> blob of nasty C code. I'd rather stand on the shoulders here than
> trying to mess with it myself.
>
>
> --
> J.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110719/9eec0ebc/attachment.htm>