Hi, can anyone tell me if there is a performance or other difference between boost::interprocess::shared_memory_object and boost::interprocess::windows_shared_memory? With the version of boost we were using back in 2011 ( boost 1.48 ), we found that windows_shared_memory operated faster than shared_memory_object when transporting around 10MB of data. Is this still the case? Thanks, Patrick
El 20/02/2014 11:42, Patrick Steele escribió:
Hi, can anyone tell me if there is a performance or other difference between boost::interprocess::shared_memory_object and boost::interprocess::windows_shared_memory? With the version of boost we were using back in 2011 ( boost 1.48 ), we found that windows_shared_memory operated faster than shared_memory_object when transporting around 10MB of data. Is this still the case? Thanks,
Nothing has changed AFAIK. shared_memory_object is a memory mapped file whereas windows_shared_memory is backed by the pagefile. I don't know why Windows should make one faster than the other, though. Best, Ion
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
El 20/02/2014 11:42, Patrick Steele escribió:
Hi,
can anyone tell me if there is a performance or other difference between boost::interprocess::shared_memory_object and boost::interprocess::windows_shared_memory? With the version of boost we were using back in 2011 ( boost 1.48 ), we found that windows_shared_memory operated faster than shared_memory_object when transporting around 10MB of data. Is this still the case? Thanks,
Nothing has changed AFAIK. shared_memory_object is a memory mapped file whereas windows_shared_memory is backed by the pagefile. I don't know why Windows should make one faster than the other, though.
Best,
Ion _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On Thu, 20 Feb 2014 17:39:54 +0100, Patrick Steele
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.
You may as well use profiler to find bottlenecks and contribute to make boost better (if the bottlenecks are in boost) instead of relying on tests with the single specific windows machine/configuration. Regards, Slava
___________________________________
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
-----Original Message-----
From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Slava
Sent: Friday, February 21, 2014 2:14 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] [interprocess] Shared memory object
On Thu, 20 Feb 2014 17:39:54 +0100, Patrick Steele
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.
You may as well use profiler to find bottlenecks and contribute to make boost better (if the bottlenecks are in boost) instead of relying on tests with the single specific windows machine/configuration. Regards, Slava _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
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
participants (4)
-
Davies, John
-
Ion Gaztañaga
-
Patrick Steele
-
Slava