Closed Bug 450666 Opened 17 years ago Closed 17 years ago

Increase intervals for long-running tests

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rdoherty, Assigned: anodelman)

References

Details

Attachments

(2 files)

In order to reduce the amount of data the graph server needs to store/retrieve, we need to increase the interval for long running tests. First idea is tests that run for more than 10 minutes can have their intervals increased to once every 10 seconds?
I'm running some tests on talos stage to only poll for memory/cpu information every 20 seconds. I'll compare the test results taken with different granularities to determine if we are losing any valuable information by polling less.
Priority: -- → P2
I'm not seeing much difference in the numbers by sampling less frequently. I think that this is pretty low risk and will reduce the amount of data sent to the graph server by a given talos cycle pretty dramatically.
Attachment #336106 - Flags: review?(rdoherty)
Comment on attachment 336106 [details] [diff] [review] [Checked in]sample memory/cpu only every 20 seconds instead of every second I'm not sure I should be reviewing this patch. I've never touched or seen this code before.
Attachment #336106 - Flags: review?(rdoherty) → review?(bhearsum)
Attachment #336106 - Flags: review?(bhearsum) → review+
Comment on attachment 336106 [details] [diff] [review] [Checked in]sample memory/cpu only every 20 seconds instead of every second /cvsroot/mozilla/testing/performance/talos/sample.config,v <-- sample.config new revision: 1.18; previous revision: 1.17 done
Attachment #336106 - Attachment description: sample memory/cpu only every 20 seconds instead of every second → [Checked in]sample memory/cpu only every 20 seconds instead of every second
Will need to keep an eye on this in case it radically alters the numbers collected.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Depends on: 457582
Looks like this got accidentally switched back to '1' at some point...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Must have happened with the patch that ensures that we run talos tests in a specific order. Need to be more careful with this main config file, since it is run everywhere.
Attachment #353343 - Flags: review?(bhearsum)
Comment on attachment 353343 [details] [diff] [review] [Checked in]sample memory/cpu only every 20 seconds instead of every second (once again) Boy, it's confusing to have dashes as valid starts of lines. Looks fine though.
Attachment #353343 - Flags: review?(bhearsum) → review+
Comment on attachment 353343 [details] [diff] [review] [Checked in]sample memory/cpu only every 20 seconds instead of every second (once again) Checking in sample.config; /cvsroot/mozilla/testing/performance/talos/sample.config,v <-- sample.config new revision: 1.22; previous revision: 1.21 done
Attachment #353343 - Attachment description: sample memory/cpu only every 20 seconds instead of every second (once again) → [Checked in]sample memory/cpu only every 20 seconds instead of every second (once again)
Attachment #353343 - Flags: checked‑in+
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: