Slow initial startup on Django project

2006-04-21 Thread Clint Ecker
Hey everyone, I'm not considering this a "problem" so much as it's annoying.  I moved a project I'd been running locally under mod_python to a shared server (on Dreamhost) using fcgi.  I've noticed that when I first visit the site, it takes somewhere between 1-10 seconds to actually load the index of my app.  I know the HTTP server is responding quickly because, well, I have it htaccess password protected and that pops up immediately, and I have a ton of other sites on this same server with no slow startup issues.
Any ideas about what causes this "slow startup" phenomena? Is it just inherent to fcgi or is there something wrong with how I'm doing business.  Thanks in advance! ---Clint Ecker
[EMAIL PROTECTED]http://phaedo.cx

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django users" group.  To post to this group, send email to django-users@googlegroups.com  To unsubscribe from this group, send email to [EMAIL PROTECTED]  For more options, visit this group at http://groups.google.com/group/django-users  -~--~~~~--~~--~--~---


Re: Slow initial startup on Django project

2006-04-21 Thread Jacob Kaplan-Moss

On Apr 21, 2006, at 7:45 AM, Clint Ecker wrote:
> Hey everyone, I'm not considering this a "problem" so much as it's
> annoying.  I moved a project I'd been running locally under  
> mod_python to a
> shared server (on Dreamhost) using fcgi.  I've noticed that when I  
> first
> visit the site, it takes somewhere between 1-10 seconds to actually  
> load the
> index of my app.  I know the HTTP server is responding quickly  
> because,
> well, I have it htaccess password protected and that pops up  
> immediately,
> and I have a ton of other sites on this same server with no slow  
> startup
> issues.
>
> Any ideas about what causes this "slow startup" phenomena? Is it just
> inherent to fcgi or is there something wrong with how I'm doing  
> business.

Does this only happen on the first couple of requests?

If so, it's most likely just the startup costs of the Python  
interpreter, Django, the database connection, and the operating  
system loading everything into caches.  That is, normal.

(I also wouldn't expect to get great performance out of Dreamhost;  
I've had no end of headaches diagnosing performance issues there.)

Jacob

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---



Re: Slow initial startup on Django project

2006-04-21 Thread arthur debert

Clint, I believe this is a fcgi thing. Dreamhost kills it after a
perdiod of inactivity, which means that the first request after a few
minutes of stillness has to load django & everything else.

Later request should respond better. There are mixed reviews on
dreamhost and django on this list, quite a few topics bring this up. It
seems to depend a little in which server you are (I am on pound, and
haven't had any issues). But at any rate you are not going to achieve
*great* performance on django. 

hope that helps, 
arthur


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---



Re: Slow initial startup on Django project

2006-04-21 Thread Adrian Holovaty

On 4/21/06, arthur debert <[EMAIL PROTECTED]> wrote:
> But at any rate you are not going to achieve
> *great* performance on django.

I assume you left "...on Dreamhost" off that sentence by mistake. I've
had fantastic performance on Django on several servers (both Linux and
Solaris). Frankly, it knocks the crap out of any other
dynamic-language framework I'm aware of, performance-wise.

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---



Re: Slow initial startup on Django project

2006-04-21 Thread arthur debert

Oh My!

my bad. yes that should read..
" are not going to achieve *great* performance on DREAMHOST."

I just meant to say that dreamhost has nice price / feature ration but
it's just a little unreliable to host a *critical* site on it.

Isn't it great that you could just read through my mistake (and have no
doubs that I was talink about dreamhost...)?

cheers


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---



Re: Slow initial startup on Django project

2006-04-22 Thread Jeremy Jones

On Fri, 21 Apr 2006 08:35:44 -0700
"arthur debert" <[EMAIL PROTECTED]> wrote:

> 
> Oh My!
> 
> my bad. yes that should read..
> " are not going to achieve *great* performance on DREAMHOST."
> 
> I just meant to say that dreamhost has nice price / feature ration but
> it's just a little unreliable to host a *critical* site on it.
> 
> Isn't it great that you could just read through my mistake (and have
> no doubs that I was talink about dreamhost...)?
> 
> cheers

One way that I've found to keep the "startup performance" thing in
check is to write a checker bot on my home server that hits a simple
page every 5 minutes.  That keeps it alive pretty much, so the only
time I get the dreaded 1-10 second startup penalty is when I kill
everything and start it up from scratch.  Once you figure out the ins
and outs of FastCGI on Dreamhost, it's really not so bad.

- jmj

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---



Re: Slow initial startup on Django project

2006-04-22 Thread Julio Nobrega

  I had *many* problems with Django on Dreamhost the first two weeks
that my systems ran there. Suddenly there are no more... I don't know
what they did, what I did, or anything else.

  There's a page on the Dreamhost panel for you to vote on new
features that they should add. Maybe +1 on an "official" Django
support (like they have for RoR) would help.


On 4/21/06, Clint Ecker <[EMAIL PROTECTED]> wrote:
> Any ideas about what causes this "slow startup" phenomena? Is it just
> inherent to fcgi or is there something wrong with how I'm doing business.
> Thanks in advance!


--
Julio Nobrega - http://www.inerciasensorial.com.br

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---