Closed Bug 1110168 Opened 10 years ago Closed 10 years ago

Enable fuzzing on linux AWS machines

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Assigned: catlee)

Details

Attachments

(1 file)

fuzz-buildbot-configs.patch
1.83 KB, patch
massimo
: review+
catlee
: checked-in+
Details | Diff | Splinter Review 
We didn't enable fuzzing initially on AWS machines because we were using all ondemand instances, and weren't sure of the cost impact.

Now we're generally running on spot instances, and we pay about $0.0325/hr for spot builders.

Fuzzing jobs take a maximum of 35 minutes to run, and we'll trigger up to 24 fuzzing jobs per hour. So this is a maximum of 24 extra CPU hours per hour, which is 576 hours per day. At $0.0325/hr, this works out to $18.72 per day.

I'm willing to turn this on and monitor it to make sure we're not overshooting this.
Attachment #8534997 - Flags: review?(mgervasini)
Assignee: nobody → catlee
Attachment #8534997 - Flags: review?(mgervasini) → review+
Attachment #8534997 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Since turning this on we've run 110 hours of fuzzing jobs on AWS machines. Definitely reasonable cost-wise.
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: