I don't know all *that* much about apache, but it sounds as though its operating in a single-thread, single process fashion. Maybe you could use mod_rewrite to redirect the uploads to another server with a shared file system. Essentially, separate the web server from the upload server.

Good luck, and keep us posted,
Lloyd Brown



Adam Olsen wrote:

Ok, I have found the culprit, though I don't know why it's happening. When someone uploads an image, all the other requests wait until the upload is complete. I've confirmed this by watching the process list and uploading a 19MB image. While this is uploading, I can watch the waiting processes build up. The moment I hit stop in the browser, they all go away. Really weird.

Nathan wrote:

So if I understand correctly: apache, mysql, and the image processing
are done on one machine.

Are you running a modern version of top that shows you i/o usage?  If
your stuff is disk-intensive (databases, storing images or temp files
tend to be) or network intensive (need a bigger pipe?), your processor
may just be waiting for i/o to feed it.

If you're using a modern version of 'top', fire it up and check the
'wa' (WAiting on I/O) percentage.

Here's what an idle server of mine shows:
Cpu(s): 1.0% us, 0.5% sy, 0.0% ni, 98.3% id, 0.0% wa, 0.0% hi, 0.2% si

~ Nathan

On 11/23/05, Adam Olsen <[EMAIL PROTECTED]> wrote:

No, just 1 machine for now (we ordered 3 more yesterday).

Adam

Nathan wrote:


--------------------
BYU Unix Users Group http://uug.byu.edu/
The opinions expressed in this message are the responsibility of their
author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to