Hello Jan, I just posted a message mentioning this issue yesterday but did not receive any feedback yet.
I don't understand why this issue has not been reached before as this is a critical performance issue that everybody should encounter as soon as working with an object having several 1:many fields. Personally I've an object with 5 1:many relations and I'm rapidly falling in OutOfMemoryException even with a small database (10 objects in each child means a result set of 100.000 records !!!) Hope we get some feedback on this. Regards, Benjamin. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: vendredi 15 mars 2002 11:51 To: [EMAIL PROTECTED] Subject: [castor-dev] Performance Issue JDO (repost sorta) There seems to be a problem with the way querry builder constructs querries. Considder this example: Instance of Class Parent has - 1000 Class ChildA instances and - 1000 Class ChildB instances. JDO retrieves objects in one querry, the querrys resultset will contain 1 x 1000 x 1000 rows (lazy load or not). For JDO to "consume" all these rows takes an enourmous amount of bandwidth, CPU on database server and CPU on JDO app server. Alternatively JDO could retrieve objects in 3 querries resulting in 1 + 1000 + 1000 rows. Is this performance issue something core developers will address ? If not; Can I make the changes and check them into CVS ? Regards Jan H. Hansen ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
