[Webkit-unassigned] [Bug 21272] Switching between custom allocators (TCmalloc, JEmalloc) in linux-qt

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=21272





--- Comment #19 from Zoltan Horvath <zoltan at webkit.org>  2010-02-09 04:47:26 PST ---
(In reply to comment #18)
> What's the current position of WebKit on switching the memory allocator? As
> described in your blog article "War of allocators in JavaScriptCore", adding
> jemalloc makes no sense for Linux-qt build. However, in Windows CE, jemalloc
> gives almost 2x speedup in page loading time over the system malloc because the
> system malloc is simply too slow.  
> 
> Is it okay to use jemalloc at least for Windows CE? If the answer is yes, I
> will file a bug for this.

Custom allocation framework is ready (only few (<5) classes aren't inherited
from FastAllocBase), so you can safely use custom allocators - trough
FastMalloc - without overriding global operator new/delete.
Now, I'm benchmarking JEmalloc on multi-threaded benchmarks,  tomorrow I'll
write a post about the results. 

First, I think we should make TCmalloc's implementation WinCE compatible, and
test that. Adding and maintaining an extra allocator - because of one platform
- is not a good idea.

What are the depedencies of enabling TCmalloc on WinCe? TCmalloc uses
pthreads... This might be a problem, isn't it?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.