ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@gridgain.com>
Subject Re: Very slow cache query compared to H2
Date Fri, 24 Mar 2017 12:14:54 GMT
Also, I'm pretty sure that 7220 milliseconds is the result you are getting
on the "cold"
JVM. Try warming it up before you are making any benchmarks (i.e. try
running at least
50000 queries before you run actual benchmark).

Best Regards,

On Fri, Mar 24, 2017 at 11:14 AM, Andrey Mashenkov <amashenkov@gridgain.com>

> Hi Zaid,
> Have you try to run query on MySQL or H2 in client server mode?
> In your test, there is an additional overhead on network round-trip and
> data serialization\deserialization. Ignite is designed as distributed
> storage, so complex SQL queries should run faster while you adding new
> nodes.
> You can try add more nodes and make some of your cached partitioned to get
> a speed-up due to query will be run in multiple threads (on multiple
> nodes). Speed-up will be as much noticeable as more data should be
> looked-up by data engine. Also you can try to rise up SQl query parallelizm
> level that available from ignite-1.9 to run query in multiple threads
> within single node.
> Comparing to Mysql, Ignite gives you failover distributed storage with
> full ACID out-of-the-box for free.
> Of course, it has lacks in some scenarios. E.g. for now, it has bigger
> overhead for simple queries than anyone would expected, but most of SQL
> engine lacks can be overcome with
> carefully data distribution planing and using fast key-value engine in
> some cases.
> So, if you plan to use some distributed solution (not Ignite only) you
> should test it in environment as much closer to production as possible, not
> just a execution time of one query on single node.
> Thanks.
> On Fri, Mar 24, 2017 at 9:06 AM, zaid <zaid.saeedi.khan@gmail.com> wrote:
>> Hi,
>> Thanks for your time looking into the issue. I have modified SlowQuery
>> program and now you should get 10 records as query response.
>> SlowQuery.java
>> <http://apache-ignite-users.70518.x6.nabble.com/file/n11405/
>> SlowQuery.java>
>> My concern is that we need to decide whether we should continue using
>> MySQL
>> or switch to Ignite SQL.
>> MySQL takes 56 milliseconds to execute the query whereas SQL grid takes
>> 7220
>> milliseconds in client server mode for my use case.
>> Are there any optimizations I can do to reduce Ignite SQL execution time
>> with respect to configuration?
>> Regards,
>> Zaid
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Very-slow-cache-query-compared-to-H2-tp11013p11405.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message