On Sat, Feb 5, 2011 at 4:59 PM, AlexS <[email protected]> wrote: > I'm running up an application on open bd 1.4 and hitting some > scalability issues. I firstly had to tweak my memory settings because > the app wanted a lot more RAM, what uses less than 200mb on BD.NET > will still run out of memory at 768mb allocated so theres clearly a > leak. >
Well, let's not get ahead of ourselves. I think you'll have to take a few steps back here and answer a few questions. 1. What are your exact JVM memory settings? Saying "768MB allocated" doesn't tell us *which* memory setting that is. 2. Probably neither here nor there since Java and .NET are two completely different beasts, but you're saying this is the exact same CFML code performing the exact same actions on the exact same data that you're running on both BD .NET and OpenBD? 3. What type of environment are you running this on? Windows? Linux? Tomcat? Jetty? Did you run an installer or did you deploy a WAR file? Probably most importantly let's not jump to any conclusions with statements like "clearly there's a leak" when we don't have any clue what's going on at this point. It could well be the app is just doing things that aren't going to work given your memory settings or the environment on which it's running. > > Plus I can just hit the same page url which is performing the same CMS > task over and over and watch the memory climb. What CMS? What's the page doing? > I get a mixture of > strange Yellow OpenBD Internal errors Without details on the exact errors it's impossible to troubleshoot. > then eventually the typical out > of memory ones complaining about either heap or the time spent in GC. > Now we're kind of getting somewhere, but knowing more about the app, the full details of the environment you're running on, the memory settings, what else is going on on the box, etc. will help. > > My gut at this stage is it relates to a large xmlobject persisted in > APP scope and the weird and wonderful ways we interact with it. > Well that certainly could be--I don't know enough about BD .NET to say for sure but if this tends to happen when you're crunching large amounts of XML it could be that depending on what your'e doing the XML in its entirety is getting loaded into memory perhaps even on every request for all we know at this point, which is why details about specifically what the code is doing and what the memory settings are is important, as well as specifically how much XML we're talking about. As an aside, I have an app that processes a huge amount of XML, some files of which are quite large, and crunching XML can be rather memory intensive. Once I gave the app plenty of memory for what it specifically needs to do everything runs incredibly well. The bottom line is that this sort of tuning is *very* application specific, and we can help point you in one direction or another based on what your code is doing. At this point if you can provide specific info on your environment, the installation type, the memory settings, the error messages, what the code is doing, and any other relevant details we'll do our best to get to the bottom of it. Matt -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- tag/function ref: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
