Hello! The main document for query optimization is https://apacheignite-sql.readme.io/docs/performance-and-debugging
For example, have you tried increasing queryParallelism on your caches? Regards, -- Ilya Kasnacheev вт, 18 дек. 2018 г. в 20:53, kellan <[email protected]>: > Hi, I'm not sure how I could make this more efficient. I'm already joining > on > every column in the key. If I try to change the ordering so that EVENTDATE > and EVENTHOUR precede the affinity key (PARENTS2CELLID), then the query > optimizer selects only the affinity key for the join. > > It seems like unless I want to partition by time, which doesn't fit my use > case, my query times for any number of rows is going to grow as I add more > time-series data. > > This doesn't seem like a very big data set to me, and with plenty of > compute > at my disposal, it seems like Ignite is performing well under the level of > a > simpler database solution like Postgres. > > Can you point me to a resource that covers indexing and query optimizing in > Ignite? I need to find a way to return a result set like this in under a > second without having to worry too much about the size of the data set. > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
