Has anyone ever tried to create a way to instrument field accesses?  I
am thinking of ways to determine candidates for deferred columns and
lazy relationships and query times.  Currently data optimizations are
an art, you need to know when and how your data is used, then you
usually create mock ups of optimizations scenarios and then implement
them in your code and compare timings.

If you could flip a switch and turn on instrumenting you could get
back hard data during real usage.  It wouldn't solve the whole puzzle
but it would help point out problem areas.

-jeff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SQLElixir" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlelixir?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to