You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Zhengqingzheng <zh...@huawei.com> on 2016/04/11 11:37:47 UTC

答复: re: Ignite Sql Query performance problem

Dear Val, 
I found another post that you have answered : http://apache-ignite-users.70518.x6.nabble.com/problem-run-jar-file-td1973.html
And solved my problem by adding several extra jar files on server side libs folder.

Best regards,
Kevin

-----邮件原件-----
发件人: vkulichenko [mailto:valentin.kulichenko@gmail.com] 
发送时间: 2016年4月11日 13:12
收件人: user@ignite.apache.org
主题: Re: re: Ignite Sql Query performance problem

Kevin,

Each index add memory overhead. It's hard to estimate without knowing the details of the application, but in general indexes do not add more than 20-30% to the overall data size.

BTW, if you can replace query with a simple get(), you should do this. It will be more effective from both performance and memory consumption standpoint. Use SQL for more complicated requests.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Sql-Query-performance-problem-tp4031p4045.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.