From c9f468c1f09eede5e9cd1f23cf55fea3b01c86d1 Mon Sep 17 00:00:00 2001 From: "darin@chromium.org" Date: Wed, 9 Dec 2009 23:55:13 +0000 Subject: Reduce kMaxPaintRects to test impact on single-core bot. TBR=brettw BUG=29589 TEST=none Review URL: http://codereview.chromium.org/479015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34204 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/renderer/paint_aggregator.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'chrome/renderer') diff --git a/chrome/renderer/paint_aggregator.cc b/chrome/renderer/paint_aggregator.cc index ebe6314..125f7b5 100644 --- a/chrome/renderer/paint_aggregator.cc +++ b/chrome/renderer/paint_aggregator.cc @@ -32,7 +32,7 @@ static const float kMaxRedundantPaintToScrollArea = 0.8f; // start combining paint rects (see CombinePaintRects). This limiting is // important since the WebKit code associated with deciding what to paint given // a paint rect can be significant. -static const size_t kMaxPaintRects = 10; +static const size_t kMaxPaintRects = 5; gfx::Rect PaintAggregator::PendingUpdate::GetScrollDamage() const { // Should only be scrolling in one direction at a time. -- cgit v1.1