Caolan McNamara

I’ve now received my 20th near identical spam mail about “I recently bought a Samsung Wave S8500 with Samsung Bada OS when will your software be available for it”. I beginning to feel a deep dislike of the device and its OS. A word to the wise, If this is a guerilla marketing attempt, then it’s going badly wrong.

Taking Alan Ning STL performance comparison of VC9, VC10 and STLPort I converted it over for Linux (available here) and compared the built in STL of gcc 4.5.1 on x86_64 versus STLPort 4.5 both at -O2. Tests and test-descriptions below are lifted directly from Alan. Times are actually in milliseconds, not seconds, but I didn’t bother regenerating the graph legends.

Lower bars are better, hardware is an i7 with 6 gigs memory.

The test for vector involves three operations – insertion, iterator traversal, and copy.

Native STL consistently faster.

Native STL consistently faster.

The test for string involves three operations – string copy, substring search, and concatenation.

Native STL apparently worse with strings with approx more than 3200 characters.

Native STL typically slower.

The test for map involves insertion, search, and deletion.

Native STL typically worse with maps over 200 elements.

Native STL typically faster.

The test for Deque comes with a twist. The deque is implemented is as a priority queue through make_heap(), push_heap() and pop_heap(). Random items are inserted and removed from the queue upon each iteration.

Native STL faster.

Native STL faster.

In general the gcc STL looks comparatively good with the exception of large maps.

Cedrics’s LibreOffice first-week codeswarm video is just so cool