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: > > Is mysql or your image processing done on another physical machine? > > If so, check the cpu/disk usage on those machines. > > > > On 11/23/05, Adam Olsen <[EMAIL PROTECTED]> wrote: > > > >>Someone posted a rather obvious and unexpected article in the Wall > >>Street Journal regarding our company yesterday. So... we suddenly have > >>growing pains. > >> > >>I'm wondering what tweaks we can do to the server/apache2/mysql to help > >>out. We are using perl and libgd to do some image processing (just > >>resizing photos from digital cameras). > >> > >>Apache becomes unresponsive when there are tons of apache process, but > >>the CPU is usually around 90% idle. There's plenty of ram left, and the > >>server is very responsive on the command line. > >> > >>Any ideas? > >> > >>Adam > >> > >>-------------------- > >>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 > >> > > > > > > -------------------- > > 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 > > -------------------- > 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 > -------------------- 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
