[
https://issues.apache.org/jira/browse/IGNITE-8925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532657#comment-16532657
]
ASF GitHub Bot commented on IGNITE-8925:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4301
IGNITE-8925
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8925
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4301.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4301
----
commit 0a829af33a93fe74521dc76a300eac096a08e4f4
Author: devozerov <vozerov@...>
Date: 2018-07-04T12:01:38Z
Fixed.
----
> SQL: Limit default number of threads for CREATE INDEX to 4
> ----------------------------------------------------------
>
> Key: IGNITE-8925
> URL: https://issues.apache.org/jira/browse/IGNITE-8925
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.7
>
>
> Currently we allocate {{CPUs/4}} cores for index creation. On powerful
> machines we may allocate too much threads, so that "Maximum number of
> retries" error start to appear in {{BPlusTree}}.
> We need to limit default number of allocated cores to 4, because:
> - Our original benchmarks shown that >4 cores do not give significant boost
> (due to retries and page splits)
> - Avoid "too much retries" error
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)