ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Sql query performance with partitioned caches
Date Wed, 27 Jan 2016 23:24:26 GMT
On Wed, Jan 27, 2016 at 5:34 AM, Andrey Nestrogaev <
a.nestrogaev@flexsoft.com> wrote:

> Denis,
> I don't agree that extra newtork roundtreeps "costs almost nothing" for
> heavy OLTP load :)

I disagree, because many large companies, including some very well known
banks, use Ignite exactly for OLTP workloads. If you look at the data grid
market, then you will quickly realize that no other data grid vendor or
project comes even close to the SQL capabilities provided by Ignite.

Again, Ignite already supports non-collocated SQL (will be released in
version 1.6 as part of IGNITE-1232
<https://issues.apache.org/jira/browse/IGNITE-1232>), but the performance
of the non-collocated joins may be worse than for the collocated joins
depending on the result sets.

In your design, you need to aim to achieve about +50% collocation for your
queries. Generally, the more collocated queries you have, the better the
performance will be. However, it is OK to have a smaller number of queries,
or the queries that are not executed often, as non-collocated queries.


View raw message