Bugzilla

(In reply to Pete Moore [:pmoore][:pete] from comment #9)

> I think this can be that the Windows images themselves are performing some expensive first-boot initialisation (e.g. if workers are installing toolchains on first boot, rather than having the toolchains burned into the machine image). That would be an issue with the machine images created by Mozilla, rather than Azure hardware being slow per se.

With the changes that landed this week, there has been a significant change in the time between VM start up and worker-runner starting. We gone from 30+ minutes to around 2 minutes. 

Using [gj8qrccqrz60aij](https://my.papertrailapp.com/systems/13939828550/events?focus=1634332406196609044&selected=1634332561666875401)/ [vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv](https://my.papertrailapp.com/groups/1141234/events?focus=1634333211771420681&q=vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv) as an example. 

[first log](https://my.papertrailapp.com/systems/13939828550/events?focus=1634332406188220420&selected=1634332406188220420):
Sep 01 11:20:32 gj8qrccqrz60aij.reddog.microsoft.com Microsoft-Windows-TerminalServices-LocalSessionManager Local multi-user session manager received system shutdown message 
Name change to match worker name:

First worker runner log
 Sep 01 11:22:16 gj8qrccqrz60aij.reddog.microsoft.com MaintainSystem StartWorkerRunner :: end - 2023-09-01T18:22:15.8625364Z 

Name change takes effect on the next start up: 
Sep 01 11:21:10 gj8qrccqrz60aij.reddog.microsoft.com MaintainSystem Check-AzVM-Name :: Name changed to vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv

(In reply to Pete Moore [:pmoore][:pete] from comment #9)

> I think this can be that the Windows images themselves are performing some expensive first-boot initialisation (e.g. if workers are installing toolchains on first boot, rather than having the toolchains burned into the machine image). That would be an issue with the machine images created by Mozilla, rather than Azure hardware being slow per se.

With the changes that landed this week, there has been a significant change in the time between VM start up and worker-runner starting. It has gone from 30+ minutes to around 2 minutes. 

Using [gj8qrccqrz60aij](https://my.papertrailapp.com/systems/13939828550/events?focus=1634332406196609044&selected=1634332561666875401)/ [vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv](https://my.papertrailapp.com/groups/1141234/events?focus=1634333211771420681&q=vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv) as an example. 

[first log](https://my.papertrailapp.com/systems/13939828550/events?focus=1634332406188220420&selected=1634332406188220420):
Sep 01 11:20:32 gj8qrccqrz60aij.reddog.microsoft.com Microsoft-Windows-TerminalServices-LocalSessionManager Local multi-user session manager received system shutdown message 
Name change to match worker name:

First worker runner log
 Sep 01 11:22:16 gj8qrccqrz60aij.reddog.microsoft.com MaintainSystem StartWorkerRunner :: end - 2023-09-01T18:22:15.8625364Z 

Name change takes effect on the next start up: 
Sep 01 11:21:10 gj8qrccqrz60aij.reddog.microsoft.com MaintainSystem Check-AzVM-Name :: Name changed to vm-au94c9yrrh2uqrsqasgrdguc1x4oxnq9ejv