Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(460)

Issue 6635004: Test impact of using default windows allocator... (Closed)

Created:
9 years, 9 months ago by jar (doing other things)
Modified:
9 years, 7 months ago
Reviewers:
CC:
chromium-reviews, brettw-cc_chromium.org
Visibility:
Public.

Description

Test impact of using default windows allocator I'll revert this as soon as the builds kick off. I just want to look at perf impact. I'll ceate a fancier CL that uses different allocators for render vs browser, but I wanted an overall baseline for transitioning completely from TCMalloc to the default allocator on Windows. TBR=cpu Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=77066

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M base/allocator/allocator_shim.cc View 1 chunk +1 line, -1 line 0 comments Download

Powered by Google App Engine
This is Rietveld 408576698