I've been trying to estimate how caching would influence the performance of my app. This app has a lot of parent-child relationships in different configurations, i.e. each object have childs in a bag, and mapped (two one-many relations). During the test I've added about 1000 objects randomly selecting the parent from the total set of objects already persisted. That resulted in an object tree of depth of about 8-12.
I wanted to test this app by reducing database communication, so I've created a test envirnoment that almost everything was cacheable - objects and relations among them. It appeared that flushing this 1000 objects took several minutes, although the same test without caching could take seconds. As I profiled it CompositeCache.get() accounted for 96.06% of total application time. How is that that writing object to _in-memory_ cache takes even longer than storing it in db? What should be avoided when planning caching strategy? -- Mike ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
