Re: Best way to find MAX value of field in Near cache

Hi, Sorry yes you are right - it does seem to work. I had seen the post below: http://apache-ignite-users.70518.x6.nabble.com/How-sql-works-for-near-cache-td30518.html Where the answer says “ SQL doesn't work with near caches at all” but I guess this is wrong. Thanks! -- Sent from: http://ap

Best way to find MAX value of field in Near cache

Hi, I have a replicated cache that is fronted by a near cache in my client (data loader) application. In this cache I have an integer field which is used as a lookup key into the cache. I am using IgniteAtomicSequence to generate this lookup key (since I believe there is no such thing as an auto i

Re: Performance on Windows vs Linux

Thanks. Not so easy to describe the PoC due to confidentiality. But it involves writing a lot of data as fast as possible at the start of the day, with persistence enabled, then with incremental updates throughout the day, and with many user queries on top through SQL (sorry I know that is probably

Performance on Windows vs Linux

Hi, I am about to start a proof of concept on Ignite and we have the option of deploying either on Windows Server 2016 or Red Hat Linux 7. I know that Ignite can be deployed on both, but is there reason to pick one over the other? Is performance better on a particular environment? We are using na

Ignite Load Performance when memory exhausted

Hi, I am evaluating Apache Ignite for a use case where I know we may not have enough RAM to store the entire database. For example we might store 30 days of data, but only have enough memory for 15, and in fact most of the queries will be against the last 5 days of data. I am doing some tests load

Query using IN Clause slow

Hi, I am seeing poor performance on queries which use IN in the WHERE clause with multiple items supplied. I have searched for issues related to this and I have seen replies suggesting that when you use IN, that indexes are not used, but I guess this must have been fixed because I do see indexes b

Re: Index usage on Joins

Thanks for your suggestion - I tried it but overall the query was slower using this method. The best approach I have found is to put the items from the group index directly on the table to avoid having to do the join. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Index usage on Joins

Hi, I am evaluating Ignite for a data warehouse style system which would have a central very large "fact" table with potentially billions of records, and several "dimensions" that describe the data. The fact table would be partitioned as it is large, and the dimensions would be replicated across a