The sounds of TCmalloc in QtLauncher
Now, I want to show you the effect of TCmalloc on some bencmhark suites... In the most cases I used QtLauncher (QtWebKit, Qt-4.6.0) to measure the results. All performace results are in msecs and the memory consumption shows the maximum resident set size (RSS) in kbytes.
QtWebKit Performance Utilities - loading tests
The first benchmark is a modified version of the QtWebKitPerformanceUtilities which is maintained by Zecke. I benchmark, the loading tests which measure the loading time of web pages without rendering. This benchmark suite uses a special webserver, which mirrors real web content and serves the benchmark. All benchmarks run on the offical r53510 WebKit revison.
As the chart shows, the loading is faster a bit with TCmalloc than with the system allocator, but it uses more memory to achive this performance gain. This tendency suits for all of my measurements, the question is on the rates only. Is it worth to use TCmalloc?
TCmalloc performs better than System malloc with more than 7% speedup, but the memory consumption grows by 11% (it's only ~6Mbytes for 9 pages...). I think we could say that this is a good and acceptable result...
SunSpider in QtLauncher
Let's see the results of the SunSpider online benchmark:
TCmalloc yields almost 7% performance improvement on this benchmark also, but on the other side memory consumption grows by 15%.
V8 in QtLauncher
Changes on V8 benchmark:
In this case, TCmallos doesn't achive a real performance gain, but the memory consumption grows by 3.5% which means more than 5MB plus memory.
WindScorpion in QtLauncher
TCmalloc gives a 13% better performance result than the system's default allocator and the memory loss is only 6.9%, which means only 3MB plus used memory.
I've put all results into the table below:
The next steps will be to tweak TCmalloc parameters or try out some other allocators. :-)