[
https://issues.apache.org/jira/browse/ARROW-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438503#comment-16438503
]
ASF GitHub Bot commented on ARROW-2458:
---------------------------------------
robertnishihara commented on issue #1893: ARROW-2458: [Plasma] Use one thread
pool per PlasmaClient
URL: https://github.com/apache/arrow/pull/1893#issuecomment-381360785
I think the approach in this PR makes sense since. @pitrou the problem that
you point exists regardless because we already give each client its own thread
pool when the clients are isolated in different processes, and this preserves
the behavior when the clients are in the same process.
One thing that could help (though I would prefer doing it in a separate PR)
is to let the user pass in the thread pool size to the constructor.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> [Plasma] PlasmaClient uses global variable
> ------------------------------------------
>
> Key: ARROW-2458
> URL: https://issues.apache.org/jira/browse/ARROW-2458
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Plasma (C++)
> Affects Versions: 0.9.0
> Reporter: Philipp Moritz
> Assignee: Philipp Moritz
> Priority: Major
> Labels: pull-request-available
>
> The threadpool threadpool_ that PlasmaClient is using is global at the
> moment. This prevents us from using multiple PlasmaClients in the same
> process (one per thread).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
