You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Shaomin Zhang <Sh...@tudor.com> on 2016/02/26 11:38:09 UTC
SQL query performance
Hi All
I am doing a SqlFieldQuery on a single cache of around 60 entries on a single Ignite server locally. The query has two parameters and the cache has a compound index of the two parameter field. It takes from 60 to 80 milliseconds to finish, while it takes only 3 milloseconds for the same query in the H2 web console from the same Ingite session. The query string and the screen shot of the H2 web session are listed below.
Is the 60 -80 ms performance normal in Ignite? If not, what might the problem?
Thank you
Shaomin
select TradeOrder._key from "TradeOrder".TradeOrder where TradeOrder.traderId = 417 and TradeOrder.orderId = 12476420
[cid:image001.png@01D17081.C8CAA1B0]
_________________________________________________________
This email, its contents, and any attachments transmitted with it are intended only for the addressee(s) and may be confidential and legally privileged. We do not waive any confidentiality by misdelivery. If you have received this email in error, please notify the sender immediately and delete it. You should not copy it, forward it or otherwise use the contents, attachments or information in any way. Any liability for viruses is excluded to the fullest extent permitted by law.
Tudor Capital Europe LLP (TCE) is authorised and regulated by The Financial Conduct Authority (the FCA). TCE is registered as a limited liability partnership in England and Wales No: OC340673 with its registered office at 10 New Burlington Street, London, W1S 3BE, United Kingdom
RE: SQL query performance
Posted by vkulichenko <va...@gmail.com>.
Hi Shaomin,
If you're doing a benchmark, you should run the code that you're going to
measure. The warm up happens on JVM level, it's not about Ignite and its
caches at all.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-query-performance-tp3202p3312.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
RE: SQL query performance
Posted by Shaomin Zhang <Sh...@tudor.com>.
Thank you very much Val.
In terms of the warning up, do I need to warm up every cache, or warning up on one cache will produce 0ms on all caches?
Shaomin
-----Original Message-----
From: vkulichenko [mailto:valentin.kulichenko@gmail.com]
Sent: 26 February 2016 18:56
To: user@ignite.apache.org
Subject: Re: SQL query performance
Hi Shaomin,
Before starting to provide best performance, JVM needs some time to warm up and apply all JIT optimizations. It sounds like you're running the query only once, so this doesn't happen. Do this several times in a loop and you should get 0ms timings.
-Val
--
View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_SQL-2Dquery-2Dperformance-2Dtp3202p3206.html&d=CwICAg&c=lcVbikor4usg5Rj5OmznbA&r=TO3grc1lvgRzUij7SCtFhBPVz_ocKy44E1ncA3VjNmM&m=sbsYZuOdbtp1azmw-UVDUdd-vYUbC64wZLe5Jn-uHTY&s=Ljrz09tKaYvhE01V9lIzVwhj8NzxUu9rDAeUjq1u2bs&e=
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
_________________________________________________________
This email, its contents, and any attachments transmitted with it are intended only for the addressee(s) and may be confidential and legally privileged. We do not waive any confidentiality by misdelivery. If you have received this email in error, please notify the sender immediately and delete it. You should not copy it, forward it or otherwise use the contents, attachments or information in any way. Any liability for viruses is excluded to the fullest extent permitted by law.
Tudor Capital Europe LLP (TCE) is authorised and regulated by The Financial Conduct Authority (the FCA). TCE is registered as a limited liability partnership in England and Wales No: OC340673 with its registered office at 10 New Burlington Street, London, W1S 3BE, United Kingdom
Re: SQL query performance
Posted by vkulichenko <va...@gmail.com>.
Hi Shaomin,
Before starting to provide best performance, JVM needs some time to warm up
and apply all JIT optimizations. It sounds like you're running the query
only once, so this doesn't happen. Do this several times in a loop and you
should get 0ms timings.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-query-performance-tp3202p3206.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.