- The crash rates on chromebot are comparable for builds with and without tcmalloc. The crash rate for tcmalloc build is higher but it seems within error margin. - Wtih tcmalloc disabled, there are some promising data from Purify test run and ChromeBot run with full page heap enabled. These are still under further investigation. - The performance results are same as last time we compared. With tcmalloc, the most perf gain is from page-cycler-moz: 15% improvement (with 25% more memory usage). The perfor gain on page-cycler-more-js is 4%, as we see tcmalloc has no perf impact on V8 benchmark. The performance gain on DOM is significant: from score 325 to 414.
r22251 re-enables tcmalloc on trunk. We can merge 22080 to dev branch if needed. Huan On Fri, Jul 31, 2009 at 6:51 PM, cpu<[email protected]> wrote: > > What are the results of this experiment? > > On Jul 30, 12:15 pm, Huan Ren <[email protected]> wrote: >> I just submitted a change (22080) that disables tcmalloc used on >> Windows platform. The plan is keeping it in trunk for 24 hours and >> then reverting it. The intentions are >> - Having another round of performance comparison between build with >> and w/o tcmalloc. >> - Having a full run of UI test under purify with tcmalloc disabled. >> - Getting a verified CL in case we'd like to build an alternative >> dev build w/o tcmalloc for A/B test. >> >> As a head up, the performance, stability, and purify test results >> could be different during the period. >> >> Huan > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
