Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.incubator.apache.org
Date: Mon, 17 Aug 2015 13:28:11 -0700 (PDT)
From: javadevmtl <java.dev.mtl@gmail.com>
To: user@ignite.incubator.apache.org
Message-ID: <1439843291263-1014.post@n6.nabble.com>
In-Reply-To: 
 <CA+eZwrErHrdcfzrRSparoOR7af_8b0Q+02K1S6a46z7Rbk4-4g@mail.gmail.com>
References: 
 <CA+eZwrGd_jtdLBqKsrxjZx4OR5pO1SxdyvGjJkeFrgYKtaj89w@mail.gmail.com>
 <1439839891847-1010.post@n6.nabble.com>
 <CA+eZwrErHrdcfzrRSparoOR7af_8b0Q+02K1S6a46z7Rbk4-4g@mail.gmail.com>
Subject: Re: Query performance
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi, thanks

2 nodes as indicated in the original thread.

I'm pretty sure I have @QuerySqlField(index = true)


But I would still expect a specific constant response time up to a certain
amount of records instead of off the start line the query time degrades from
0-30K records there something going on...

I need to do count(distinct someField) where another field = ? It's doable
using put/get but then I would need to keep track of individual keys for
each count I want to do. So for a single entry I need 18 different keys to
track unique counts for each property.

Now if we can do analytics style queries using indexes in real time that
would be huge! Especially in the couple milliseconds!


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