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

Issue 300014: Reliablity test... (Closed)

Created:
11 years, 2 months ago by Nirnimesh
Modified:
9 years, 7 months ago
Reviewers:
huanr, Allen
CC:
chromium-reviews_googlegroups.com, tim (not reviewing), Paweł Hajdan Jr.
Visibility:
Public.

Description

Reliablity test Introduce a flag --noclearprofile to instruct reliability test to not clear profile before firing off the browser. This is so avoid unnecessary disk writes. (The default value of this flag is OFF, so win reliability bot should continue to behave as is). Mac Chromebot would fire several instances of Chrome at a time, and I want to minimize the load it generates. I understand that I should begin with a clean profile, so I clean-up the user-data-dir after every few runs, rather than cleaning every single time. BUG=25271 TEST=reliability_tests should work as is on Win

Patch Set 1 #

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -0 lines) Patch
M chrome/test/reliability/page_load_test.cc View 1 5 chunks +7 lines, -0 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Allen
LGTM Just wondering, how much does this impact your throughput?
11 years, 2 months ago (2009-10-21 00:59:20 UTC) #1
Nirnimesh
11 years, 2 months ago (2009-10-21 01:01:57 UTC) #2
On 2009/10/21 00:59:20, Allen wrote:
> LGTM
> 
> Just wondering, how much does this impact your throughput?

Not a lot when I run continuous URLs without firing off the browser each time,
but significantly if I do. I see disk usage ~10 MB/s with 15 parallel instances
all loading one url.

Powered by Google App Engine
This is Rietveld 408576698