Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: upstream sync #15

Merged
merged 33 commits into from
May 20, 2024
Merged

chore: upstream sync #15

merged 33 commits into from
May 20, 2024

Conversation

abhijit-hota
Copy link
Member

No description provided.

erik-bershel and others added 30 commits May 10, 2024 13:31
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
)

Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
)

Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
…9862)

The bug that prompted enabling 8.3 filename creation was fixed 5 years ago, see dotnet/android#3407:
> Fix included in Xamarin.Android 10.1.0.30.
>
> Fix included on Windows in Visual Studio 2019 version 16.4.

We're on VS 2019 16.11: https://github.com/actions/runner-images/blob/98150396188d19c21a7d7c596cf4a4d7609bb12a/images/windows/Windows2019-Readme.md?plain=1#L233

8.3 filename creation is known to hurt file creation performance, especially when there are a large number of similarly named files in the same folder:
* https://learn.microsoft.com/en-us/archive/blogs/josebda/windows-server-2012-file-server-tip-disable-8-3-naming-and-strip-those-short-names-too
* https://www.linkedin.com/pulse/dont-forget-disable-short-filenames-83-servers-folders-wes-brown
* https://deep.data.blog/2013/06/19/debugging-story-slowness-due-to-ntfs-short-file-8-3-name-generation/

I created a new VM with the base Azure Marketplace Windows 2019 image and confirmed that 8.3 name generation is disabled by default for both the OS and temp disk:
```
fsutil 8dot3name query C:
The volume state is: 1 (8dot3 name creation is disabled).
The registry state is: 2 (Per volume setting - the default).

Based on the above settings, 8dot3 name creation is disabled on C:

fsutil 8dot3name query D:
The volume state is: 1 (8dot3 name creation is disabled).
The registry state is: 2 (Per volume setting - the default).

Based on the above settings, 8dot3 name creation is disabled on D:
```

This might help a bit with actions/cache#752, although I haven't tested it, and AFAICT it's unlikely make an order of magnitude difference.
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Co-authored-by: Image generation service account <[email protected]>
Co-authored-by: Actions service account <[email protected]>
Copy link
Collaborator

@prajjwaldimri prajjwaldimri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎹

@abhijit-hota abhijit-hota merged commit aa111b2 into main May 20, 2024
5 of 6 checks passed
@abhijit-hota abhijit-hota deleted the upstream-sync branch May 20, 2024 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants