[infinispan-dev] ISPN-863 - Thoughts / Questions

[david marion]

same result.
 


Date: Mon, 17 Jan 2011 11:54:15 -0300
From: vblagoje at redhat.com
To: infinispan-dev at lists.jboss.org
Subject: Re: [infinispan-dev] ISPN-863 - Thoughts / Questions


Its easier to run everything from command line for two reason I can think of:
- everyone has same env to compare results with you
- it is all ready to go

See http://community.jboss.org/wiki/InfinispanandMaven

On 11-01-17 11:38 AM, Dave wrote: 




All,
 
I am trying to test some changes that I made using Eclipse and the TestNG plugin. I am not familiar with TestNG. Are there any settings that I should make? Any ideas?
 
java.lang.OutOfMemoryError: Java heap space
      at org.infinispan.util.concurrent.BoundedConcurrentHashMap$HashEntry.newArray(BoundedConcurrentHashMap.java:295)
      at org.infinispan.util.concurrent.BoundedConcurrentHashMap$Segment.<init>(BoundedConcurrentHashMap.java:898)
      at org.infinispan.util.concurrent.BoundedConcurrentHashMap.<init>(BoundedConcurrentHashMap.java:1367)
      at org.infinispan.container.DefaultDataContainer.<init>(DefaultDataContainer.java:78)
      at org.infinispan.container.DefaultDataContainer.<init>(DefaultDataContainer.java:47)
      at org.infinispan.container.DefaultDataContainer.unBoundedDataContainer(DefaultDataContainer.java:93)
     at org.infinispan.factories.DataContainerFactory.construct(DataContainerFactory.java:53)
      at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:315)
      at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:251)
      at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:840)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:225)
      at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:120)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:192)
      at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:323)
      at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:251)
      at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:840)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:225)
      at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:120)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:192)
      at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:323)
      at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:251)
      at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:840)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:225)
      at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:120)
      at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:192)
     at org.infinispan.factories.InternalCacheFactory.bootstrap(InternalCacheFactory.java:92)
      at org.infinispan.factories.InternalCacheFactory.createAndWire(InternalCacheFactory.java:78)
      at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:62)
      at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:510)
      at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:440)
      at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:409)
      at org.infinispan.config.ConfigurationValidationTest.testDefaultMemoryGuardConfiguration(ConfigurationValidationTest.java:100)
 
 
 
-----Original Message-----
From: infinispan-dev-bounces at lists.jboss.org [mailto:infinispan-dev-bounces at lists.jboss.org] On Behalf Of Vladimir Blagojevic
Sent: Friday, January 14, 2011 11:05 AM
To: infinispan -Dev List
Subject: Re: [infinispan-dev] ISPN-863 - Thoughts / Questions
 
Hey David,

First of all kudos for taking on such a non-trivial task!

On 11-01-14 12:22 AM, david marion wrote: 
1.      Modify configuration in some way so that the following can be specified:
a.       The percentage value of used JVM memory (i.e. 95) at which entries should be evicted to try and avoid an OOM error.
b.      The number of items that should be evicted when memory reaches this threshold
2.      Modify LRU and LIRS Eviction class so that the accessQueue member can be accessed by the new Eviction class so that two access queues don’t have to be maintained.
3.      Create a new Eviction class, a subclass of  LIRS, where the accessQueue is used from the Eviction strategy the user specifies and the for loop in the execute method is exited when the evicted set equals value from 1.b above.
4.      Modify DataContainerFactory.construct() to call DefaultDataContainer.boundedDataContainer() regardless of eviction policy. This will always create a BoundedConcurrentHashMap

I don't think you have to extend LRU and LIRS, as long as you implement EvictionPolicy you are fullfilling the contract. What extending LRU and LIRS can do is give you some order in selecting proper elements for eviction. I think the precise technical term in research literature is "eviction precision". 



1.       
2.      Create an instance of the new Eviction class in each segment.
3.      Modify BoundedConcurrentHashMap.Segment put and replace methods such that when new values are going to be put into the Segment, the memory usage is checked and the execute method is called on the new Eviction class.

Sounds right!



1.       
 
Questions:
 
1.      What are the implications of using a BoundedConcurrentHashMap instead of a ConcurrentHashMap when maxEntries is set to -1?

I think none except you turn on eviction by using BoundedConcurrentHashMap.



1.       
 
Thoughts
 
1.      This will not guarantee that an OOM error does not occur. It will attempt to guard against an OOM caused by putting new values into the cache. This will probably be more effective when the cache is being used in client/server mode, and less effective when used in embedded mode as to other code running in the JVM.
 
 
-- Dave Marion
 

Cheers,
Vladimir
_______________________________________________
infinispan-dev mailing list
infinispan-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev

_______________________________________________ infinispan-dev mailing list infinispan-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110117/56f333b9/attachment-0001.html