[
https://issues.apache.org/jira/browse/ARROW-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Farmer reassigned ARROW-12903:
-----------------------------------
Assignee: (was: Weston Pace)
This issue was last updated over 90 days ago, which may be an indication it is
no longer being actively worked. To better reflect the current state, the issue
is being unassigned. Please feel free to re-take assignment of the issue if it
is being actively worked, or if you plan to start that work soon.
> [C++] Create new thread pool benchmark demonstrating the "scheduling"
> bottleneck
> --------------------------------------------------------------------------------
>
> Key: ARROW-12903
> URL: https://issues.apache.org/jira/browse/ARROW-12903
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: C++
> Reporter: Weston Pace
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The benchmark ThreadPoolSpawn (in thread_pool_benchmark.cc) is used to help
> understand the cost of adding a new thread task and to know when it is worth
> it / not worth it to schedule additional work. For example, it seems that
> for small (1000) task sizes we start to lose the benefit of threads in as few
> as 2 threads.
> However, this benchmark is actually demonstrating a worst-case scenario in
> terms of "scheuduling" overhead. Without changing the thread pool
> implementation at all we can considerably improve the efficiency of this
> benchmark. This Jira is to add an alternative best-case scenario to better
> help understand the cost of new thread tasks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
