Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #2951

Re: Multiprocessing, shared memory vs. pickled copies

Show all headers | View raw

On 4/10/2011 9:11 AM, Miki Tebeka wrote:
>> Now, I don't know that I actually HAVE to pass my neural network and
>> input data as copies -- they're both READ-ONLY objects for the
>> duration of an evaluate function (which can go on for quite a while).
> One option in that case is to use "fork" (if you're on a *nix machine).
> See http://pythonwise.blogspot.com/2009/04/pmap.html for example ;)

    Unless you have a performance problem, don't bother with shared
memory.

    If you have a performance problem, Python is probably the wrong
tool for the job anyway.

				John Nagle

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: Multiprocessing, shared memory vs. pickled copies Miki Tebeka <miki.tebeka@gmail.com> - 2011-04-10 09:11 -0700
  Re: Multiprocessing, shared memory vs. pickled copies John Nagle <nagle@animats.com> - 2011-04-10 09:27 -0700
    Re: Multiprocessing, shared memory vs. pickled copies sturlamolden <sturlamolden@yahoo.no> - 2011-04-10 15:29 -0700
      Re: Multiprocessing, shared memory vs. pickled copies John Nagle <nagle@animats.com> - 2011-04-11 00:21 -0700
        Re: Multiprocessing, shared memory vs. pickled copies sturlamolden <sturlamolden@yahoo.no> - 2011-04-11 12:11 -0700
          Re: Multiprocessing, shared memory vs. pickled copies sturlamolden <sturlamolden@yahoo.no> - 2011-04-11 12:25 -0700

csiph-web