[Numpy-discussion] Shared memory ndarrays (update)

srean srean.list at gmail.com
Mon Apr 11 14:11:39 EDT 2011


Apologies for adding to my own post. multiprocessing.Array(...) uses an
anonymous mmapped file. I am not sure if that means it is resident on RAM or
the swap device. But my original question remains, what are the pros and
cons of using it versus numpy mmapped arrays. If  multiprocessing.Array is
indeed resident in memory (subject to swapping of course) that would still
be advatageous compared to a file mapped from a on-disk filesystem.

On Mon, Apr 11, 2011 at 12:42 PM, srean <srean.list at gmail.com> wrote:

> Hi everyone,
>
>   I was looking up the options that are available for shared memory arrays
> and this thread came up at the right time. The doc says thatmultiprocessing
> .Array(...) gives a shared memory array. But from the code it seems to me
> that it is actually using a mmap. Is that correct a correct assessment, and
> if so, is there any advantage in using multiprocessing.Array(...) over
> simple numpy mmaped arrays.
>
> Regards
>   srean
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20110411/d1cba104/attachment.html>


More information about the NumPy-Discussion mailing list