This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Use FileStream's ctor instead of File.Open when all access is synchronous #5680
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Can you use a named parameter for buffer size throughout?
…nous Several places in our libraries use use File.Open* methods. These are simple wrappers for FileStream's constructors, and all use the default "useAsync" value of true (this varies from the the full framework, where the default is false). When only using synchronous Stream methods, a value of true is pure overhead, as each Read/Write/Flush method needs to schedule the asynchronous operation and then block waiting for it to complete. In the few places we're using File.Open* in this manner, I've changed them to instead use FileStream's ctor directly, to avoid the unnecessary access overheads.
|
For a couple of these I am concerned that we don't actually have an async API. In particular the ZipArchive ones. Those can be some pretty expensive blocking reads. |
|
I agree. I think it's certainly worthwhile looking at adding additional async compression APIs. Until that happens, though, I think the changes in this PR are pure goodness. Agreed? |
|
Yeah, LGTM. I filed an issue on adding APIs. |
|
LGTM |
stephentoub
added a commit
that referenced
this pull request
Jan 26, 2016
Use FileStream's ctor instead of File.Open when all access is synchronous
15 tasks
picenka21
pushed a commit
to picenka21/runtime
that referenced
this pull request
Feb 18, 2022
Use FileStream's ctor instead of File.Open when all access is synchronous Commit migrated from dotnet/corefx@d214ddb
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several places in our libraries use use File.Open* methods. These are simple wrappers for FileStream's constructors, and all use the default "useAsync" value of true (this varies from the the full framework, where the default is false). When only using synchronous Stream methods, a value of true is pure overhead, as each Read/Write/Flush method needs to schedule the asynchronous operation and then block waiting for it to complete. In the few places we're using File.Open* in this manner, I've changed them to instead use FileStream's ctor directly, to avoid the unnecessary access overheads.
cc: @ericstj, @ianhays, @mellinoe