Hi,
Yes, you are right, if you decrease the property (sqlOnheapRowCacheSize),
you get sacrificing performance.
But default value is really great:
public static final int DFLT_SQL_ONHEAP_ROW_CACHE_SIZE = 10 * 1024;
You can try to analyse heap dump, in order to make sure in the reason of
the
It seems if I set this number to property to 1 can't set it to zero then the
heap size does not grow. I am assuming we are sacrificing performance for
this. Is there still an issue with Ignite code or is this desired behavior.
--
View this message in context:
Here is how i am constructing that query
SqlQuery SQL_PAGE_QUERY = new
SqlQuery(TiffPage.class, "documentId = ? AND pageNumber = ?");
--
View this message in context:
I have isolated my issue to the cache configuration of indexed types. If I
remove setting the indexed type property the heap gets cleaned up. If I
leave this property in only about 10 to 15% of the heap gets cleared on any
garbage collection. Do I have something configured wrong regarding this
More information but here is a complete dump of the cache configuration for
this particular cache.
ImageCache Cache Configuration settings"CacheConfiguration [name=ImageCache,
storeConcurrentLoadAllThreshold=5, rebalancePoolSize=2,
rebalanceTimeout=1, evictPlc=null, evictSync=false,
Hi Thanks for getting back so quick we are trying to get this into production
and it is holding us up. I should have clarified our environment setup. We
will have two tomcat applications configured as server nodes. We will have
5 client nodes. The client nodes are the ones doing the work and the
Hi Styriver!
At the first glance, the following line is suspicious:
Ignition.setClientMode(true);
You shouldn't use it as a Client node. It should be Server node, mean
Ignition.setClientMode(false);
You can find here
I should add we need to run in Replicated mode but as a test I switched to
local mode and we did not see the heap increasing as we ran repeated load
tests.
--
View this message in context:
We have a cache configured as Replicated OFF_HEAP_TIERED and when we execute
our load test we watch Heap space grow in JConsole to the point where the
application becomes unresponsive when it reaches heap limit. We see no signs
in JConsole or Cache Metrics that off heap is growing?
Here is our