Skip to content

Conversation

@stecrain
Copy link
Contributor

@stecrain stecrain commented Jul 26, 2019

Use the win32 api to check file write time instead of the winrt api.
The particular winrt api used previously is a brokered api, resulting in a cross-process call just to check the file write time.

fixes #2806

Microsoft Reviewers: Open in CodeFlow

@stecrain stecrain requested a review from a team as a code owner July 26, 2019 00:51
@ghost ghost added the vnext label Jul 26, 2019
@stecrain stecrain changed the title Speed up file write time check. Speed up file write time checks for bytecode caching Jul 26, 2019
@acoates-ms acoates-ms merged commit 81da772 into microsoft:master Jul 26, 2019
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.

[Performance Bug] Bytecode caching in vnext uses brokered APIs to check file properties.

2 participants