On Mon, October 23, 2006 13:57, loufoque wrote:
Ovanes Markarian wrote:
we have some application, where boost::shared_ptr is extensively used.
shared_ptr is rather slow, indeed. You should consider changing your design if the speed is a problem.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Well, I must admit, that a problem was with different loop variables set. One var (whereshared_ptr was used) had one ZERO more in its decimal value.... What a shame! Sorry guys! But I am happy now. Now with default macros used, shared_ptr is about 10% slower. If I use the quick allocator the speed is only 8% slower. If I enable both macros (single-threaded and quick-allocator) shared_ptr is quicker as an implementation without shared_ptr. My question now would be if you plan or it is already possible to have a policy for specifying Threading and Allocator? With Kind Regards, Ovanes Markarian