Re: LoadCache Performance decreases with the size of the cache

Hi Val, first of all, let me thank you for this great product and incredible mailing list. Anonymizing our code will take a bit longer but I can give the following numbers: load time 10M records without indexes 10m2s load time 10M records with a simple row id type index : 12m load time 10M

Analyzing clustered data with Tableau BI

Thanks to Igor Sapego we finally prepared and polished technical documentation for the integration in between Apache Ignite and well know BI tool - Tableau. Enjoy ;) https://apacheignite-mix.readme.io/docs/tableau Prachi, please do the final

Re: LoadCache Performance decreases with the size of the cache

Hi Steve, Currently this is not possible. If what you're saying is true, then in probably make sense to add such option, but I want to reproduce it myself first. Can you at least provide timings for different dataset sizes with and without indexes? A reproducer would be even better. Also are you

Re: WARNING: Failed to load 'igniteshmem' library from classpath. Will try to load it from IGNITE_HOME. WARNING: Failed to start shared memory communication server.

Hi Ankit, If shared memory library is not loaded, nodes will simply switch to TCP and everything will work fine. Actually, shared memory communication is known to be not very stable, so usually we recommend to disable it. Most likely it will not be default anymore in 2.0, or probably will be even

Re: LoadCache Performance decreases with the size of the cache

Hello guys, I finally understood what the "problem" is. With 20 millions of records, the indexing time is very expensive. Is there a way, like for a database, to disable indexing during load time and to re-enable it after loading? I guess that rebalancing the b-trees (or whatever is used to

Re: NullPointerException on ScanQuery

Hi Dmitry. Thank you. On Fri, Dec 23, 2016 at 2:50 PM, dkarachentsev wrote: > Hi Alper, > > This is caused because of race. NPE happens between two events: removing > affinity nodes and change cache state to STOPPED. In other words: > 1. Remove affinity nodes; >

Re: NullPointerException on ScanQuery

Hi Alper, This is caused because of race. NPE happens between two events: removing affinity nodes and change cache state to STOPPED. In other words: 1. Remove affinity nodes; -- Start scan query. 2. Start exchange; 3. Change cache state. I've opened a ticket for that [1]. [1]