ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: Local Node Query Optimization
Date Wed, 19 Aug 2015 07:03:14 GMT
Thats quite interesting. May be slowdown was due to GC activity? How large
your dataset was in that test?

No, editing H2 url is explicitly prohibited, there are quite a few things
you can brake and most probably you will not improve anything much.
If you are interested, you can hack on Ignite source code, I will be happy
to accept your patch if you will find something useful.


2015-08-19 2:16 GMT+03:00 JohnnyS <jtksai@gmail.com>:

> Sergi
> By using setSqlOnheapRowCacheSize(100000) in the cache configuration the
> distinct query time went from 200 ms to 30 ms when using off-heap. For the
> ONHEAP_TIERED the query time was originally 120 ms with the same optimized
> query time. I think I could live with these numbers considering that I will
> be running the queries in parallel. I think the problem is that for
> millions
> of rows, majority of data will not be in heap and the queries will be
> slowish for these.
> I couldn't find how to change the H2 settings through the cache
> configuration. Can I edit the H2 url somehow?
> Regards,
> j.
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Local-Node-Query-Optimization-tp996p1043.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message