Python2: multiprocessing.dummy.Pool vs multiprocessing.pool.ThreadPool
In python 2, is there any difference between multiprocessing.dummy.Pool and multiprocessing.pool.ThreadPool? The source code seems to imply they're the same.
python python-2.7 threadpool python-multiprocessing python-multithreading
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
add a comment |
In python 2, is there any difference between multiprocessing.dummy.Pool and multiprocessing.pool.ThreadPool? The source code seems to imply they're the same.
python python-2.7 threadpool python-multiprocessing python-multithreading
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
add a comment |
In python 2, is there any difference between multiprocessing.dummy.Pool and multiprocessing.pool.ThreadPool? The source code seems to imply they're the same.
python python-2.7 threadpool python-multiprocessing python-multithreading
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
In python 2, is there any difference between multiprocessing.dummy.Pool and multiprocessing.pool.ThreadPool? The source code seems to imply they're the same.
python python-2.7 threadpool python-multiprocessing python-multithreading
python python-2.7 threadpool python-multiprocessing python-multithreading
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
edited Nov 20 at 16:47
ShadowRanger
57.3k45094
57.3k45094
asked Nov 20 at 16:42
user1071847
283514
asked Nov 20 at 16:42
user1071847
283514
asked Nov 20 at 16:42
user1071847
283514
283514
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
They're the same (both on Py2 and Py3); multiprocessing.dummy.Pool is just a thin wrapper that imports and calls multiprocessing.pool.ThreadPool. The actual code is just:
def Pool(processes=None, initializer=None, initargs=()):
from multiprocessing.pool import ThreadPool
return ThreadPool(processes, initializer, initargs)
In general, I'd prefer using multiprocessing.dummy.Pool only because the existence of multiprocessing.dummy is officially documented, where multiprocessing.pool is not (it's an internal implementation detail).
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397632%2fpython2-multiprocessing-dummy-pool-vs-multiprocessing-pool-threadpool%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
They're the same (both on Py2 and Py3); multiprocessing.dummy.Pool is just a thin wrapper that imports and calls multiprocessing.pool.ThreadPool. The actual code is just:
def Pool(processes=None, initializer=None, initargs=()):
from multiprocessing.pool import ThreadPool
return ThreadPool(processes, initializer, initargs)
In general, I'd prefer using multiprocessing.dummy.Pool only because the existence of multiprocessing.dummy is officially documented, where multiprocessing.pool is not (it's an internal implementation detail).
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
add a comment |
They're the same (both on Py2 and Py3); multiprocessing.dummy.Pool is just a thin wrapper that imports and calls multiprocessing.pool.ThreadPool. The actual code is just:
def Pool(processes=None, initializer=None, initargs=()):
from multiprocessing.pool import ThreadPool
return ThreadPool(processes, initializer, initargs)
In general, I'd prefer using multiprocessing.dummy.Pool only because the existence of multiprocessing.dummy is officially documented, where multiprocessing.pool is not (it's an internal implementation detail).
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
add a comment |
They're the same (both on Py2 and Py3); multiprocessing.dummy.Pool is just a thin wrapper that imports and calls multiprocessing.pool.ThreadPool. The actual code is just:
def Pool(processes=None, initializer=None, initargs=()):
from multiprocessing.pool import ThreadPool
return ThreadPool(processes, initializer, initargs)
In general, I'd prefer using multiprocessing.dummy.Pool only because the existence of multiprocessing.dummy is officially documented, where multiprocessing.pool is not (it's an internal implementation detail).
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
They're the same (both on Py2 and Py3); multiprocessing.dummy.Pool is just a thin wrapper that imports and calls multiprocessing.pool.ThreadPool. The actual code is just:
def Pool(processes=None, initializer=None, initargs=()):
from multiprocessing.pool import ThreadPool
return ThreadPool(processes, initializer, initargs)
In general, I'd prefer using multiprocessing.dummy.Pool only because the existence of multiprocessing.dummy is officially documented, where multiprocessing.pool is not (it's an internal implementation detail).
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
answered Nov 20 at 16:46
ShadowRanger
57.3k45094
57.3k45094
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
add a comment |
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
Thanks for stating your preference as to which to use.
– user1071847
Nov 20 at 17:09
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397632%2fpython2-multiprocessing-dummy-pool-vs-multiprocessing-pool-threadpool%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
