Python multiprocessing with pathos

前端 未结 2 1211
遇见更好的自我
遇见更好的自我 2020-12-13 20:36

I am trying to use Python\'s pathos to designate computations into separate processes in order to accelerate it with multicore processor. My code is organized like:

2条回答
  •  离开以前
    2020-12-13 21:21

    I'm the pathos author. I'm not sure what you want to do from your code above. However, I can maybe shed some light. Here's some similar code:

    >>> from pathos.multiprocessing import ProcessingPool
    >>> class Bar:
    ...   def foo(self, name):
    ...     return len(str(name))
    ...   def boo(self, things):
    ...     for thing in things:
    ...       self.sum += self.foo(thing)
    ...     return self.sum
    ...   sum = 0
    ... 
    >>> b = Bar()
    >>> results = ProcessingPool().map(b.boo, [[12,3,456],[8,9,10],['a','b','cde']])
    >>> results
    [6, 4, 5]
    >>> b.sum
    0
    

    So what happens above, is that the boo method of the Bar instance b is called where b.boo is passed to a new python process, and then evaluated for each of the nested lists. You can see that the results are correct… len("12")+len("3")+len("456") is 6, and so on.

    However, you can also see that when you look at b.sum, it's mysteriously still 0. Why is b.sum still zero? Well, what multiprocessing (and thus also pathos.multiprocessing) does, is make a COPY of whatever you pass through the map to the other python process… and then the copied instance is then called (in parallel) and return whatever results are called by the method invoked. Note you have to RETURN results, or print them, or log them, or send them to a file, or otherwise. They can't go back to the original instance as you might expect, because it's not the original instance that's sent over to the other processors. The copies of the instance are created, then disposed of -- each of them had their sum attribute increased, but the original `b.sum' is untouched.

    There is however, plans within pathos to make something like the above work as you might expect -- where the original object IS updated, but it doesn't work like that yet.

    EDIT: If you are installing with pip, note that the latest released version of pathos is several years old, and may not install correctly, or may not install all of the submodules. A new pathos release is pending, but until then, it's better to get the latest version of the code from github, and install from there. The trunk is for the most part stable under development. I think your issue may have been that not all packages were installed, due to a "new" pip -- "old" pathos incompatibility in the install. If pathos.multiprocessing is missing, this is the most likely culprit.

    Get pathos from github here: https://github.com/uqfoundation/pathos

提交回复
热议问题