You go dude!

> We have been running Apache with CF 4.5 on NT 4 for the last 2 year under
> very heavy load and have found no stability problems that were related to
> Apache.  Additionally, because of the open API of apache we have been able
> to do some very interesting things for scale and reliability:
> 
> 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.
> 
> 2. Create modules to handle high load.  We build pages in CF, then if the
> page is seeing more load than CF can handle, we write an apache module in
> C++ to handle that one function and use the Apache handler to intercept the
> ..cfm request, check if we have a custom handler for the page, handle it if
> we do, and pass it on to CF if we do not.  This is, BTW how we are able to
> set cookies during a server side redirect.
> 
> 3. Bind different virtual hosts to different ports (I do not use IIS so I do
> not know if yuo can do this or not).  Our webserver has a single IP and each
> host is a different high port (8080, 8081,8082, etc).  We handle the
> redirection from different external IP's to a single Internal IP, different
> port either in the firewall or the load balancer.  This allows the
> adding/removing of hosts without re-ip'ing the web server and limits the
> number of IP addresses which is important for some firewall licensing
> schemes.
> 
> We are firm believers in the KISS principle (keep it simple stupid).  Apache
> is pretty simple, we upgrade when we want to, and it does not try to hook
> into too many OS functions that may cause issues.
> 
> The down side is that it requires a programmer to make the most of it and
> the interface is config file based, which not everyone is comfortable with.
> 
> My $.02
> 
> Justin
> 
> Justin Greene
> Co-CEO
> ClicVU, Inc.
> 216 West 18th St., Floor 12 - NYC 10011
> P: 212-629-8900 - F: 212-629-9860
> http://www.clicvu.com
> 
> ---------------------------------------------------------------------
> Sign up for your free Spamex account:
> http://www.spamex.com
> Protect your real email address forever
> ---------------------------------------------------------------------
> 
> 
> 
> -----Original Message-----
> From: Zac [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 31, 2001 11:21 PM
> To: CF-Talk
> Subject: RE: IIS or Apache? (WAS RE: can anyone help?)
> 
> > I would recomment sticking with IIS on an NT box.  With CF
> > and Apache, there
> > were (at least for me) a bunch of bugs.
> 
> Well I think this is one of those YMMV moments. I ran Apache, CF 4.5 and
> mySQL on an NT4 server for months with no problems at all. And it was, YMMV
> again, more stable than when I was running IIS.
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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

Reply via email to