Hi Val,
Thank you for your quick response.
I checked my java class annotation, I did not add index options on the
definition.
My original java setting looks like this:
@QuerySqlField
private String objId;
After adding index flag:
@QuerySqlField(index = true)
private String objId;
it does speed up my query demo. Now, one thousand time query only take 397ms,
on average less than 1ms per query (my example dataset contains only 17,000
data records).
Thank you for your help.
One more question: what if I have multiple indexes on my table, after setting
index=true, what is the cost for the memory usage?
Best regards,
Kevin
-----邮件原件-----
发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com]
发送时间: 2016年4月11日 5:54
收件人: user@ignite.apache.org
主题: Re: Ignite Sql Query performance problem
Hi,
Most likely you don't have indexes and the query has to scan the whole cache to
find the data you're requesting. Can you show your configuration and the SQL
statement that you're executing?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Sql-Query-performance-problem-tp4031p4041.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
