Migrate from GitHub to SourceForge with this tool. Check out all of SourceForge's recent improvements.
Close

#29 Poor performance in query rereading

v2.0
closed-fixed
Core (19)
5
2004-01-18
2003-11-27
No

Hi,

There is a problem with rereading Query or Extent.

Currently, the logic works like this. When generating
a Query, columns corresponding to the DFG fields
of the target class are included in the SELECT.
Of the resulting objects, those *not* currently
instantiated in the PM get instantiated and are
given field values from the result row. Those that
are already instantiated are returned as-is.
Often, these old objects are in hollow state, so when
app wants to get some data from them it leads to
generating additional SELECTs for every object. That
leads to performance slowdown.

This logic should be made smarter such that if an
existing instance is in a Hollow or
PersistentNonTransactional
state it likewise is given field values from the Query
result row. This way we have only one SQL SELECT not
many of them.

More details here:
http://sourceforge.net/forum/forum.php?thread_id=979149&forum_id=188033

Discussion

  • Mike Martin

    Mike Martin - 2004-01-18

    Logged In: YES
    user_id=582193

    Fixed as part of a much larger refactor, just checked in.

    Mike

     
  • Mike Martin

    Mike Martin - 2004-01-18
    • assigned_to: nobody --> jackknifebarber
    • status: open --> closed-fixed
     

Log in to post a comment.