Re: Cache loading errors out

Yep, thanks for the help! Thanks, Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-loading-errors-out-tp3636p3764.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache loading errors out

Arthi, I found out that there was an issue with visor cmd that was fixed recently https://issues.apache.org/jira/browse/IGNITE-2726 The fix will be available in the next release. As per SQL performance, the offheap data is deserialized and copied to Java heap when you need to return it as a par

Re: Cache loading errors out

Thanks Denis. I could use cache.size(CachePeekMode.OFFHEAP) to the off heap entries count. The visor tool does not show the offheap entries though (I used cache -a to print the detailed stats). Just a quick check on the SQL performance. will there be noticeable difference in SQL join query runtime

Re: Cache loading errors out

Hi Arthi, /I re-ran the tests with offheap tiered settings, and it looked very neat. The heap usage was around 300MB./ //This is because all your cache data presently located out of Java heap in the offheap space [1] Offheap is very useful for cases when Java heap tends to grow to tens and h

Re: Cache loading errors out

hi Denis, I re-ran the tests with offheap tiered settings, and it looked very neat. The heap usage was around 300MB. Please find the hist attached. I could not take a profiler snapshot as it is a remote application and uses Java 7. Thanks again, Arthi hist3328.1

Re: Cache loading errors out

Arthi, Please create a memory snapshot using visual VM profiler [1] and share it with us. I need to see roots that holds the rest of the memory. [1] https://visualvm.java.net/snapshots.html Regards, Denis On 3/29/2016 4:17 PM, arthi wrote: Thanks Denis. I changed the long into int for keys

Re: Cache loading errors out

Thanks Denis. I changed the long into int for keys and also the object fields. The memory for each bitmap object is about 160-200 bytes. I can see that the memory footprint for all objects and keys comes to around 6.1 GB. The rest of the memory is still around 5GB. Can this be reduced? There is n

Re: Cache loading errors out

Hi Arthi, Why do you expect that the data total size should be around 235 MB? How did you measure this? >From the histogram I see that there are many Integer[] arrays preallocated in the heap that already occupy more than 6 GB - 3092587 6651967760 [I Do you use Integer[] arrays in your cod

Re: Cache loading errors out

Hi Arthi, Try to use Visual VM Memory Profiler to see the objects that fill the heap [1]. Alternatively you can quickly build a heap histrogram ("jmap -histo ") that will show number of objects of a particular class that are allocated. There is a chance that your custom objects "leaked" somehow.

Re: Cache loading errors out

Hi Val, I bumped up the heap for Java to 50g and it worked. I am not sure why the heap gets so large, my data size to load to cache is ~ 2gb and I dont have backups enabled. I am using binarymarshaller with compact footer disabled, as I need to get the C++ client work on this cache. C++ API gives e

Re: Cache loading errors out

Hi arthi, Did you check the memory consumption. Does JVM has the amount of memory you expect? Are there any GC pauses? As for the second error, there should be an exception on server side. Can you check the logs and show the trace? -Val -- View this message in context: http://apache-ignite-u

Re: Cache loading errors out

When I get to see the entries in Visor, I can see 100,000 entries. I have a java client to loop through the cache. But this client also fails now - Exception in thread "main" javax.cache.CacheException: Failed to run map query remotely. at org.apache.ignite.internal.processors.query.h2.twos

Re: Cache loading errors out

When I get to see the entries in Visor, I can see 100,000 entries. I have a java client to loop through the cache. But this client also fails now - Exception in thread "main" javax.cache.CacheException: Failed to run map query remotely. at org.apache.ignite.internal.processors.query.h2.twos