Hi!
H2 is optimized for what it does and it's data format, only the H2
parser is used in Ignite, if you run a single node you should expect it
to be a bit slower compared to H2, are you running a single node ?
It's only if you have multiple nodes you can expect it to be faster
(depending of course on the data and where it is located and so on).
Mikael
Den 2018-08-09 kl. 12:41, skrev the_palakkaran:
Hi,
When I tried running few db lookup scenarios in H2 and ignite, I got better
performance for H2. All were basic db operations like =, <=, >=.
These were the figures for 2million records(2 lookups for one record)
H2 : 3 minutes
Ignite (cache gets based on keys) : 3.4 minutes
Ignite (SQLFields query based) : 5 minutes
Below is my sample cache config:
cacheConfig = new CacheConfiguration<>("paramControlCache");
cacheConfig.setIndexedTypes(Key.class, Model.class;
cacheConfig.setReadThrough(false);
cacheConfig.setAtomicityMode(ATOMIC);
cacheConfig.setCacheMode(CacheMode.PARTITIONED);
cacheConfig factory = new CacheCacheFactory();
cacheConfig.setCacheStoreFactory(factory);
cacheConfig.setDataRegionName("CacheDataRegion");
cacheConfig.setOnheapCacheEnabled(true);
How does this happen? Is there something I am missing out ??
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
