hi mike,
you can create another cache with key equals (idnumber + value), redirect
your streamer to it, and then feel free to check cache size. it could waste
your RAM, but fast enough for any parallel queries, because it's not
map/reduce at all. we used this weird k/v trick in many 'ignite report
ed
@QuerySqlField(index=true)
int IdNumber;
@QuerySqlField
double value;
public aThing(int id,double val)
{
IdNumber=id;
value = val;
}
}
-Original Message-
From: slava.koptilin [mailto:slava.kopti...@gmail.com]
Sent: Monday, February 26, 2018 1
Hi Mike,
Have you checked GC log? Have you seen long pauses?
Is it possible to share SQL query and corresponding execution plan [1]?
Also, please share cache configurations.
[1]
https://apacheignite-sql.readme.io/docs/performance-and-debugging#using-explain-statement
Thanks!
--
Sent from: ht
Mike
-Original Message-
From: slava.koptilin [mailto:slava.kopti...@gmail.com]
Sent: Monday, February 26, 2018 11:17 AM
To: user@ignite.apache.org
Subject: RE: Slow Group-By
Hi Mike,
It seems that GROUP_BY requires to fetch all dataset into java heap (in order
to sort data) and it may lead to lo
Hi Mike,
It seems that GROUP_BY requires to fetch all dataset into java heap (in
order to sort data) and it may lead to long GC pauses.
I think that data collocation [1] should improve performance with using
GROUP BY.
[1] https://apacheignite.readme.io/docs/affinity-collocation
Thanks!
--
Sen
Oh, also, during the difference in time, only 1-2 cores seem to be involved.
Mike
From: Williams, Michael
Sent: Monday, February 26, 2018 9:40 AM
To: user@ignite.apache.org
Subject: Slow Group-By
All,
Any advice on speeding up group-by? I'm getting great performance before the
group-by clause
