SQL query CPU utilization too low.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

SQL query CPU utilization too low.

Andrew Mashenkov
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?
Reply | Threaded
Open this post in threaded view
|

Re: SQL query CPU utilization too low.

dsetrakyan
I am OK, as long as we have ability to turn this behavior one and off on
per-query and per-cache basis.

On Fri, Oct 28, 2016 at 12:43 PM, Andrey Mashenkov <
[hidden email]> wrote:

> 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?
>