Because of the way memory usage is related to JVM garbage collection and other processes, I agree with Barney that load testing of your whole app with your data is the best way to see if you have problems, rather than trying to put together a picture based on measurements of individual bits of the app. Packages like OpenSTA make this a repeatable and reproducible task.
On 12/8/05, Terry Ford <[EMAIL PROTECTED]> wrote: > << I'm a huge fan of the "build well, optimize later" approach to > programming. Build your app as well as you can, using the simplest > means reasonable, and be confident that the app is more than good > enough until it's objectively demonstrated not to be. >> > > Yep, that's the approach I take too. I'm constantly looking to improve > application response once something new is up and running. One of the best > ways of determining how something will act in a real environment is to let it > run in that real environment and see how it does act, and then optimize from > there. [snip] -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:226527 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
