I have no idea. Maybe clarifying the distinction between "have a process create an anonymous backed SharedArray and dispatch work over it on other processes" and "use a named non-disk (virtual file) backed SharedArray from independent processes" would assist someone else in offering a suggestion.
On Thursday, March 17, 2016 at 2:29:57 PM UTC-4, ben e wrote: > > Hello, > I have been working with IPC via shared memory in a few languages, with > Julia being my most recent and a very pleasant surprise. Accessing a > SharedArray mapped to a disk backed file (via SharedArray(file, type, dims) > ) across independent processes is very straight forward and has good > performance. > > It appears that the disk-file backed SharedArray is syncing to the file on > every write/update to the array - am I mistaken about this (I'm not > suggesting it is a problem, just want to ensure I'm clear)? > > While there are examples of how to have a process create an anonymous > backed SharedArray and dispatch work over it on other processes in the same > vm session, I haven't quite sorted out how to use a named non-disk (virtual > file) backed SharedArray from independent processes (so two separate > programs can open it and use it for IPC, as I can with the disk-file backed > version). I would like to compare the performance, as I would expect it to > be even faster. > > Is there a way to used a non disk-file backed, yet still named mmap'd file > with the current SharedArray implementations exposed? If not, is this > something that I can implement using the Mmap module? Any advice or pointer > to where I should be looking in the docs or source would be greatly > appreciated. > > Thank you for the help, > Ben > >
