11 messages in ru.sysoev.nginxRe: Re: worker_processes
FromSent OnAttachments
Šime RamovJan 29, 2007 9:07 am 
Aleksandar LazicJan 29, 2007 1:21 pm 
Šime RamovJan 29, 2007 2:32 pm 
Aleksandar LazicJan 29, 2007 6:05 pm 
Šime RamovJan 30, 2007 12:48 pm 
Aleksandar LazicJan 30, 2007 12:57 pm 
Igor SysoevJan 30, 2007 1:00 pm 
Šime RamovJan 30, 2007 2:34 pm 
Scott YangJan 30, 2007 2:49 pm 
Cliff WellsJan 30, 2007 3:11 pm 
Aleksandar LazicJan 30, 2007 11:48 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Re: worker_processesActions...
From:Šime Ramov (hi-8@public.gmane.org)
Date:Jan 29, 2007 2:32:50 pm
List:ru.sysoev.nginx

2007/1/29, Aleksandar Lazic <al-n@public.gmane.org>:

Hm this is a very difficult question, from my point of view. [...] As I have said: it isn't a easy question because there are many, many opinions about this issue ;-)

Yeah, I was expecting exactly this answer :)

4.) You *must* measure you applicaton a *easy* explanation is here: http://mongrel.rubyforge.org/docs/how_many_mongrels.html, yust think on django instead of mongrels ;-)

Thanks, that really helps a lot! I'll do some testing tomorrow.

Right now, I have one testing Django site with default worker_processes 1; and it's just blazingly fast. But note that it's just private site, for testing, on a sub-domain. It gets almost no traffic, except me and a few others.

So, I'll do some testing and adjust for a real world usage case.

Anyway, this just shows how Django and nginx is fast. It's amazing. Just one Django FastCGI threaded server and one nginx instance with one worker process sitting in front and serving static files while passing dynamic stuff to FastCGI. I just couldn't believe the speed of rendering, the site just appears :) And it's dynamic -- it grabs from SQLite db, no caching. On a 160MB RAM VPS.

- Šime