[eclipselink-users] Performance degarde on using caching option

[Kiran Kumar Gubbi <kiran.kumar@xxxxxxxxxx>]

After changing queries from nativequery to sessionquery the performance of
the application drastically degraded. Used the following setting for entity
and data access object for caching.

Entity class 

@Cache(
		type = CacheType.SOFT, 
		shared = true,
		size = 10000,
		coordinationType = CacheCoordinationType.SEND_OBJECT_CHANGES
)


DAO method ( before calling this methops List of sample objects are
available in cache)
 
public Sample getSample() {
  Sample sample = new Sample();
  sample.setNonPromaryKeyProperty1("kk");
  sample.setNonPromaryKeyProperty2("jj");

  ReadObjectQuery query = new ReadObjectQuery( Sample.class );
  query.setExampleObject( sample);
  query.checkCacheOnly();

  return ( Sample ) session().executeQuery( query );
}

This change has degraded performance by 3 times.  Any suggestion please.


Kind regards,
kiran

-- 
View this message in context: http://old.nabble.com/Performance-degarde-on-using-caching-option-tp29247519p29247519.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.