From: <je...@de...> - 2004-05-08 14:01:23
|
Most of the ISP I know propose Apache/PHP/MySQL. Do you know some who would propose Yaws instead? Or did you ever tried=20= to convice some to do so? My ISP is a co-operative ( http://ouvaton.coop ). So I _may_ have some=20= influence upon technical choices. The recent discussions here comparing Apache/PHP and Yaws seem to prove=20= that Yaws is more performant. Does it also mean that Yaws consumes less=20= memory and CPU than Apache for the same job? Let's distinguish to=20 clarify between serving static pages and dynamic pages (and I=20 understand that in the second case, the comparison is not easy). I would appreciate any argument/discussion (pro/cons) in providing Yaws=20= services in both cases (on a shared server). Thanks! J=E9r=F4me.= |
From: <mic...@er...> - 2004-05-25 15:52:01
|
On Sat, 8 May 2004 16:01:10 +0200, Jérôme Desquilbet <je...@de...> wrote: > Most of the ISP I know propose Apache/PHP/MySQL. > Do you know some who would propose Yaws instead? Or did you ever tried > to convice some to do so? > > My ISP is a co-operative ( http://ouvaton.coop ). So I _may_ have some > influence upon technical choices. > The recent discussions here comparing Apache/PHP and Yaws seem to prove > that Yaws is more performant. Does it also mean that Yaws consumes less > memory and CPU than Apache for the same job? Let's distinguish to > clarify between serving static pages and dynamic pages (and I understand > that in the second case, the comparison is not easy). Regarding efficiency, Yaws is great. It can handle a huge number of simultaneous connexion and keeps a really small memory footprint. > I would appreciate any argument/discussion (pro/cons) in providing Yaws > services in both cases (on a shared server). The only major drawback I see for launching a Yaws hosting service is security. If you have control over the Erlang node, you can launch all command you want in the Erlang VM (for example os:cmd). This can be avoided by looking some function (removing os module, etc). If you want to host multiple-users applications in one Yaws / Erlang VM you have a Yaws hosting could be provided by separating user applications and hosting them in different Erlang VM. One main Erlang VM could host the accept and dispatch process. Then however in the configuration Erlang VM are networked and users could interact with other nodes... What do you think ? Do you see other approach to do massive hosting with Yaws ? -- Mickaël Rémond http://www.erlang-projects.org/ |