Can boa or thttpd do location rewrites? At present, every URL is requested http://www.domain.com/username/imagename.jpg Internally though, it's handled as /home/httpd/www.domain.com/htdocs/sites/u/us/username/imagename.jpg Apache is doing rewrites for it to do this. I'll look into this as an option. If we could speed up the current system, then they could use the main server to serve the static images and one of the smaller systems for the dynamic content, and still have a spare for something else.
william -----Original Message----- From: Adrian Chadd [mailto:[EMAIL PROTECTED] Sent: Sunday, March 16, 2003 09:09 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [isp-caching] Re: Questions on caching or load distributing. On Sun, Mar 16, 2003, William Devine, II wrote: > List, > > I currently have a client that serves files and images on other websites. > They get around 8M-9Million image views per day with anywhere from 1 to > 3Million of them being unique views, so each file might be viewed anywhere > from once per day to some upwards of 5k times per day. Their present > system is getting highly overloaded and I'm looking for methods to > accelerate this. > > They presently serve on Linux 2.4.18-4smp from Redhat 7.3, Apache 1.3.X, > dual 1.8Ghz Xeons, 2Gigs RAM and a 3Ware ATA 100 RAID controller with Four > 80Gig 7200RPM ATA100 Drives in a RAID 5 array (1 hot spare) > The two options I'm looking at are either to make this sytem a 'file server' > for a bank of web servers, or as the central webserver for a bank of caching > proxy servers. Each of the two Servers each have one 2.4Ghz processor, 2GB > RAM and one 18Gig Ultra160 10K RPM SCSI Drives. (the hardware was already > purchased by the client and awaiting deployment.) Hi, Are they serving the images out of apache too? if so, try this: * setup images.domain.com on a seperate IP * move all images into a virtual server under there * then, once that all works, install thttpd or boa (light-weight single process webservers, great for serving lots of static content!) just to run the images.domain.com webserver This should reduce the load on the webserver quite dramatically. You might find he doesn't need to run a cluster - or perhaps moving the images onto a seperate server will free up enough resources to keep things going. I'd consider this before looking at a clustered setup. (FYI: I've had excellent results with very image-intensive websites.) Adrian -- Adrian Chadd "It shouldn't take an hour and a half for <[EMAIL PROTECTED]> "any woman to take a bath." - Captain Jerk, Women and .. ------------------------ANNOUNCEMENT----------------------------------- ----------------------------------------------------------------------- ISPCON Spring 2003 April 23-25, Baltimore, MD www.ispcon.com The Definitive Event for all wired and wireless service providers. ----------------------------------------------------------------------- ----------------------------------------------------------------------- ____________ The ISP-CACHING Discussion List ___________ To Join: mailto:[EMAIL PROTECTED] To Remove: mailto:[EMAIL PROTECTED] Archives: http://isp-lists.isp-planet.com/isp-caching/archives/ ------------------------ANNOUNCEMENT----------------------------------- ----------------------------------------------------------------------- ISPCON Spring 2003 April 23-25, Baltimore, MD www.ispcon.com The Definitive Event for all wired and wireless service providers. ----------------------------------------------------------------------- ----------------------------------------------------------------------- ____________ The ISP-CACHING Discussion List ___________ To Join: mailto:[EMAIL PROTECTED] To Remove: mailto:[EMAIL PROTECTED] Archives: http://isp-lists.isp-planet.com/isp-caching/archives/
