Oh, this reminds me. At my last setup, we had a cluster (hwlb) of servers
for cf and a separate cluster for serving images. The reason for this is
similar to below. For the image server, we stripped apache of all
unnecessary modules and tweaked the threads/size parameters to optimize
for normal image sizes. We kept all image paths in a separate application
variable and could change it all will (useful for SSL when the image
server doesn't have a certificate) - also setup up the image server to
mount the web root (like the clustered cf servers do), but only to the
images subdirectory. Kept that machine nice and basic and secure...
> 1. Run 2 instances of apache on each web server. One handles all CF
> requests and one handles all static requests (images mostly). We have found
> that apache can serve over 500 14K files per second on a dual PIII 600 (we
> were actually bottlenecked by the 100mb network. With 1K files we hit about
> 750/sec). Running 2 instances of apache allows us to have cold fusion under
> load and not slow down the delivery of all the images required to complete
> the page.
Tony Schreiber, Senior Partner Man and Machine, Limited
mailto:[EMAIL PROTECTED] http://www.technocraft.com
http://www.simplemessageboard.com ___Free Forum Software for Cold Fusion
http://www.is300.net ___________The Enthusiast's Home of the Lexus IS300
http://www.digitacamera.com ______________DigitA Camera Scripts and Tips
http://www.linklabexchange.com _____________Miata Link ECU Data Exchange
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
