Getting over excited with multiple CF instances
One of the cool things about enterprise versions of CF is the fact that you can run multiple CF instances. What I see as a benefit of this is that if one of your applications becomes problematic then it's not going to bring your other apps on the same server down. With this in mind I've been happily setting up multiple instances of CF on a server for each app. This appeares to work fine, I can restart an instance if I need to and all my other sites continue to run.... well run rather slow that is. This is the problem i've been having recently, rally slow response times.
The environment that the server is in has 4G of RAM on a windows IIS solution. Now speaking with the masterful Andy Allan, he informed me that you shouldn't really run lots of CF instances, here a quick extract from out IM:
assuming each instance is configured with it's own JVM config file, you've got [undisclosed number] instances, plus Windows (and anything else) competing for that 4gb...
he goes on to say
even adobe only run 2 instances on 64bit solaris...2 is the good number, but 3 at a push if you go with 3 you'll need to limit jvm memory to around 512-768mb
So can anyone guess what I'll be doing this afternoon? Thanks for the info Andy. It's hard to find this information around.
I don't know how much RAM we're running on the boxes, but it's safe to say that it's alot. Just bootstrapping the website on my localhost typically takes about 400MB of memory and then it'd increase from there as sessions are created and other runtime in memory variables are created.
Hope that helps.