Closed Bug 1517280 Opened 7 years ago Closed 7 years ago

Investigate using larger Moonshot disc for WIndows 10 Installs

Categories

(Infrastructure & Operations :: RelOps: Windows OS, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: markco, Assigned: markco)

Details

No description provided.
Assignee: nobody → mcornmesser

jmaher: The test associate with the link below were on moonshot nodes using the larger disk. Could you take a look and see if there is any concern on time or noise, please?

https://treeherder.mozilla.org/#/jobs?repo=try&revision=9db110a9dc357fd9073886ba5d53c4af931beb1b

Flags: needinfo?(jmaher)

I had to look over the data a couple of times, this is really cool. Overall the noise is less and I don't see any downsides. Where did this request/idea come from? Is this something we could experiment with on our unittest vms in aws- maybe excess disk allows for more cache or less aggressive disk cleanup activity/timing.

Flags: needinfo?(jmaher)

The original idea was Q because we had the larger disc sitting there not being used.

Rob: do you have any thoughts on the question of using a larger disk in aws?

Flags: needinfo?(rthijssen)

it's a pretty simple configuration change to make in order to use larger disks in aws/ec2.

on windows 10 we currently use two 120gb disks eg:

those lines can simply be modified to some other size and after we've triggered a new ami deploy, subsequently instantiated instances will have the new disk sizes. on ec2 it's worth noting that the larger you configure the disk size, the higher the provided iops will be (you get faster read/write operations).

i'm happy to make the necessary changes if someone can let me know what size in gb we're seeing better hardware test results on.

Flags: needinfo?(rthijssen)

This will be wrapped into the work with deployment of Puppet configured images. https://bugzilla.mozilla.org/show_bug.cgi?id=1545844

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.