Actually, boost::make_shared involves one dynamic_cast operation (when getting deleter from shared_ptr object), that's why it doesn't perform faster at all 2011/4/6, Nevin Liber <nevin@eviloverlord.com>:
On 6 April 2011 11:43, Phil Bouchard <philippe@fornux.com> wrote:
http://www.boost.org/doc/libs/1_46_1/libs/smart_ptr/smarttests.htm
Here's another one here comparing shared_ptr<>, intrusive_ptr<> and garbage collected algorithms: http://hnxgc.harnixworld.com/benchmarks/GCBench/
Glancing at the code, I noticed that they aren't using make_shared or allocate_shared, which any real world high performance app would most likely be using just to cut the number of allocations in half. Not a great benchmark for this kind of thing... -- Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> (847) 691-1404 _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost