Everyone's looking at the web serving mechanisms, so let me ask a relatively obvious question - are you doing anything complex database-wise on the page that's being so slow? Perhaps one of the issues is a missing index or something equivalent?
There's some good debugging information tied into pages that will show you how long it took to do the SQL statements associated with any given page render... -joe On 1/5/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
On 1/5/07, David Abrahams <[EMAIL PROTECTED]> wrote: > > "Jeremy Dunck" <[EMAIL PROTECTED]> writes: > ... > Sure. If the traffic demands were high I could understand why we'd > like to dedicate the process to Apache. But I don't think they're > high yet. I am running quite a few services off this machine (Trac > servers, Mailing lists, SVN) but they have relatively few users. You said earlier that "top" seemed to not be CPU-bound. What about "free"? What about "lsof"? I know paging seems unrelated... which is why KeepAlive was my first shot. But the "several minutes" thing sounds like Apache is spending a lot of time before deciding to spin up extra children. Can you generate load on these other services (to tie up processes), then see performance with and without KeepAlive? Trying to repro that issue will be tough. :-/ ... > > There's no need at all to run a separate machine for media. Lightty > > serving media files is crazy-fast. As long as you have a separate IP > > (and Apache is doing IP-based, rather than name-based, service), > > I'm somewhat unschooled in the IP-based/name-based distinction. I > read the docs, but I'm not sure they connected. My server has one IP > address. I am running several Apache virtual servers on that IP > address. My configuration contains > > NameVirtualHost: *:80 > > so is that name-based? Yeah, sorry. Basically, the difference is whether your web server sends responses based on IP only (in which case the vhost ServerName is window dressing) or whether it's based on HTTP's HOST header, in which case the response depends not only on IP, but also HOST. In any case, you can still set them up to listen on separate ports, even on the same IP. > > server.port = 81 > > server.bind = "the.same.ip" Then just change MEDIA_URL to be yourdomain.com:81, and you should be set. No one will be using your media directly, probably, so the :81 won't confuse people typing in URLs. ;-) >
--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
