Hi! Just to share with you all our latest experiences about performance. After three days working on OJB performance optimization for our Swing app, I've achieved a formula that fits near all our cases (look, it may not fit your need).
We are not using proxyies for everthing anymore. Today, all objects are not proxy, and references are not proxies too (99,9% of cases). Only collections (the ones you be absolutely right that will not always need data) will receive proxy="true". Example, a customer in 90% of the cases will need the addresses (1:N) reference, so we don't use proxy. At other side, we have a "per user" log feature, where we almost never ask for this info (only store new info there for future reference if needed), and in this case, we use proxy. To solve the cyclic references, we working with PerBroker cache, that works fine for this purpose. rc5 is stable and fast (the only problems I've detected is that it tries to get PersistentField even if auto-update='false', and the toString in proxies - but this is subject for other threads). Starting the app with -Xmx128m we are able to materialize about 30000 really complex objects in simple machines (800MHz-1Ghz) in less than 10 seconds (that is good to my point of view). To debug and fine tune, I'm using the p6spy and the Jahia SQL Profiler (that's incredible simple to configure OJB to use this two excellent products). Thanks to all people that always supported us in this year of research (Thomas, Armin, Jakob - by your patience - along others, need special thanks). We still have a lot of work, and from time-to-time I'll be sharing more info and knoledge with this amazing team. Richter --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.620 / Virus Database: 399 - Release Date: 11/3/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
