From my reading, the Windows version is faster but it doesn't have the persistence as the Linux version. The description mentions this:
A class that wraps the native Windows shared memory that is implemented as a file mapping of the paging file. Unlike shared_memory_objecthttp://www.boost.org/doc/libs/1_55_0/doc/html/boost/interprocess/shared_memo..., windows_shared_memoryhttp://www.boost.org/doc/libs/1_55_0/doc/html/boost/interprocess/windows_sha... has no kernel persistence and the shared memory is destroyed when all processes destroy all their windows_shared_memoryhttp://www.boost.org/doc/libs/1_55_0/doc/html/boost/interprocess/windows_sha... objects and mapped regions for the same shared memory or the processes end/crash.
Boost lets you choose what means more to you.
___________________________________
John Davies
Contractor
Home Respiratory Care
Philips Home Healthcare Solutions
1740 Golden Mile Highway
Monroeville, PA 15146
Email: john.davies@philips.com
Fax: 724-387-4109
From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Patrick Steele
Sent: Thursday, February 20, 2014 11:40 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] [interprocess] Shared memory object
Tests at the time were showing the Windows version to operate about twice as fast. If nothing has changed I guess I will remain with it then. I had just been hoping for the code to be more platform dependent.
On 20 February 2014 14:44, Ion Gaztañaga