I think it must be a maximum local parallelism level but not just `on` and `off` setting (the default is obviously 1). This along with separately configurable query thread pool will give a finer grained control over resources.
Sergi 2016-10-30 18:22 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > I already mentioned this in another email, but we should be able to turn > this property on and off on per-query and per-cache levels. > > On Sat, Oct 29, 2016 at 11:45 AM, Sergi Vladykin <sergi.vlady...@gmail.com > > > wrote: > > > Agree, lets implement such a parallelization. > > > > I think we will need an explicit setting for SqlQuery and SqlFieldsQuery, > > the default behavior should not change. > > > > Sergi > > > > 2016-10-28 22:39 GMT+03:00 Andrey Mashenkov <amashen...@gridgain.com>: > > > > > So, now we have every SQL query run on each node in single thread. This > > can > > > be an issue for heavy queries or queries running on big data sets, e.g. > > > analytical queries. > > > > > > For now, the only way to speed up such queries is to add more nodes to > > grid > > > running on same server. In this case, data will be partitioned over all > > > these nodes and query will be split and run on all nodes. > > > > > > It seems, we can have a benefit if split SQL queries locally as we do > it > > > across nodes with TwoStepQuery. > > > > > > > > > Thoughts? > > > > > >
