[
https://issues.apache.org/jira/browse/IGNITE-21809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-21809:
----------------------------------------
Description:
At the moment, intra-query parallelism is achieved by splitting the query on
several fragments in the place where distribution conversion is required, but
the fragment itself is tied up to a single thread. Such a parallelization
results in a low resource utilization by a single query, especially in case of
huge fragments like the ones containing aggregation or colocated joins.
Let's investigate possible solutions and make a POC
was:At the moment, intra-query parallelism is achieved by splitting the query
on several fragments in the place where distribution conversion is required,
but the fragment itself is tied up to a single thread. Such a parallelization
results in a low resource utilization by a single query, especially in case of
huge fragments like the ones containing aggregation or colocated joins.
> Sql. Improve intra-query parallelism
> ------------------------------------
>
> Key: IGNITE-21809
> URL: https://issues.apache.org/jira/browse/IGNITE-21809
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> At the moment, intra-query parallelism is achieved by splitting the query on
> several fragments in the place where distribution conversion is required, but
> the fragment itself is tied up to a single thread. Such a parallelization
> results in a low resource utilization by a single query, especially in case
> of huge fragments like the ones containing aggregation or colocated joins.
> Let's investigate possible solutions and make a POC
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
