Hi, >Hello, > >I've run into the problem of ODMG locking overhead and would like some >ideas about best OJB practices to deal with it (~4 minutes to retrieve >one object means something has to be done).
Indeed ! [snip] >If I understand correctly, enforcing persistence by reachability means >that once one object is retrieved, this object and all others in the >associated graph are locked. > > Does the locking extend to the contents of proxy references and proxy > collections? Proxy references are locked on materialization of the real object, i.e. the object will only be locked when you try and access it. That seems reasonable to me. Proxy collections, however, *are* materialized and locked when the object owning the collection is locked. This is going to be a problem to me too. [see http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED] e.org&msgNo=2026 and the rest of the thread] Thomas proposed a flag that would disable implicit locking of associated objects. Obviously this would mean that you would have to explicitly lock every object you were going to modify, but that seems like a good idea to me. I eagerly await this issue finding it's way to the top the ojb-dev teams to-do list ! Cheers, Charles > >What are the best ways to limit the extent of the locking in a large >graph? For example, say some classes have instances that are >created/updated often and these classes refers to other >classes that are >much more static. If the graph of the static objects is >large, locking >is a big problem. How can one keep the link between these classes and >not suffer the lock overhead? > >Your responses would be most appreciated. > >Phil > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> This email and any attachments are strictly confidential and are intended solely for the addressee. If you are not the intended recipient you must not disclose, forward, copy or take any action in reliance on this message or its attachments. If you have received this email in error please notify the sender as soon as possible and delete it from your computer systems. Any views or opinions presented are solely those of the author and do not necessarily reflect those of HPD Software Limited or its affiliates. At present the integrity of email across the internet cannot be guaranteed and messages sent via this medium are potentially at risk. All liability is excluded to the extent permitted by law for any claims arising as a re- sult of the use of this medium to transmit information by or to HPD Software Limited or its affiliates. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
