Thank you for your response. I used query parallelizm and the time reduced to ~2.3s, which is still too much. Regarding 1. is there any documentation about configuration parameters (recommended number of nodes, how much data should be stored on each node). We currently have 2 nodes with 32GB RAM each. Every 1 million records from our cache occupy about 1GB (is there a way to see how much memory a cache actually occupies? we look now at the Allocated next memory segment log info) For 3. it seems that the index is hit from the execution plan: /* "productCache".IGNITEPRODUCT_MANUFACTURERCODE_IDX */ No?
We have this issue also when we use a large OFFSET (we execute this kind of query because we want paginated results) Also, this cache will be updated frequently so we expect it to grow in size. Thank you! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-query-is-slow-tp16475p16487.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
