Hi, Why you think the performance is slow? Ignite SQL has an H2 underneath and have some overhead as it is a distributed system at first. So, local query latency can be slightly higher.
How do you measure query latency? You may need to warm grid up to all components involved in query initialize. What is a query plan? On Tue, May 29, 2018 at 2:13 PM, the_palakkaran <[email protected]> wrote: > Hi, > > I have 200 caches loaded into a single data region. Among that I have a > customerCache which has 300K records. It has many indexed fields, including > customer number. > > When I query using *SQLFieldsQuery *on this particular cache (where > condition has just customer number = ?), it takes around *280ms *to query a > customer !!!! > > This is very slow as compared to H2. > > Please provide some tips to improve the performance or let me know if I am > missing something here. > > Ignite is started in embedded mode. Tried keeping data on heap and off > heap, > there is no difference in performance. > > cache configuration as below: > > dataRegionCfg.setInitialSize(8L * 1024 * 1024 * 1024); > dataRegionCfg.setMaxSize(8L*1024*1024*1024); > dataRegionCfg.setPersistenceEnabled(false); > dataStorageCfg.setDataRegionConfigurations(dataRegionCfg); > dataStorageCfg.setPageSize(4096); > customerCacheConfig = new CacheConfiguration<>("customerCache"); > customerCacheConfig.setIndexedTypes(CustomerKey.class, > Customer.class); > customerCacheConfig.setReadThrough(false); > customerCacheConfig.setAtomicityMode(ATOMIC); > customerCacheConfig.setCacheMode(CacheMode.LOCAL); > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov
