Thanks for your thorough and thoughtful replies. - Dave
On Aug 15, 1:39 pm, Matthew Woodward <[email protected]> wrote: > Dave Anderson wrote: > > One follow-up question (and this is something I've wondered about vis- > > a-vis Adobe CF as well): what are the pros/cons of running multiple > > instances of openBD (or CF for that matter)? > > Pros are that your applications are completely isolated from one > another. Only cons really are A) you have to manage each instance > separately, so if you have something like a datasource that two apps use > you have to put it in both instances of OpenBD, and B) there's a bit > more resource utilization on the server, but honestly in my experience > this is pretty nominal. I keep meaning to do some basic load testing to > get some baseline metrics but just haven't gotten around to it yet. > > Also bear in mind that regardless of which way you go, it's *Tomcat* > that controls the JVM memory settings. So if you're used to CF Standard, > for example, don't think that each instance of OpenBD is going to take > up 768MB of RAM or anything like that. You set Tomcat memory settings, > and then all your webapps play within that space. (And note that by > default Tomcat is set to only use 64MB of RAM so you'll definitely want > to increase that.) > > Note too that there is an upper limit of what the JVM can use, so if you > have a server with tons of RAM you can even do things like run multiple > instances of Tomcat on different ports to further isolate things and use > more physical RAM than a single JVM would be able to use. > > > If this were a > > production environment and I had multiple virtual hosts, > > I'm assuming you mean multiple OpenBD instances here? > > > would I > > benefit from multiple instances in some way? Would having multiple > > instances increase the number of simultaneous requests the server is > > capable of executing? > > Total number the server can respond to, no. There's of course an upper > limit there that is shared among all the apps, and Tomcat's doing all > the thread management. > > What it would do, however, is keep one application that's maxed out the > number of threads Tomcat has allocated to it from affecting another app. > That's not a very concrete explanation I realize, but I'd have to look > deeper into Tomcat's thread management rules to give you a better > answer. ;-) The main point is that it would segregate your apps which > can provide some benefits. > -- > Matthew Woodward > [email protected]http://www.mattwoodward.com/blog > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments.http://www.gnu.org/philosophy/no-word-attachments.html > > smime.p7s > 4KViewDownload --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
