-
Notifications
You must be signed in to change notification settings - Fork 528
Write chunks async; unblock sync-waits directly #586
Conversation
0ccdd69
to
b5b7158
Compare
b5b7158
to
912be30
Compare
Also see #589 |
Nice catch. |
|
||
private struct WaitingTask | ||
{ | ||
public bool isSync; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: capitalization.
912be30
to
e6ca887
Compare
Re: the threadpool queuing for async vs not for sync blocked at some future point the tcs can use |
The IsSync and queuing SocketOutput tasks to threadpool, should be able to be skipped for 4.6+ and coreclr versions later than tomorrow's. A task post RTM when there is time and the effects can be investigated? (As the current performance characteristics are known) |
{ | ||
public bool IsSync; | ||
public int BytesToWrite; | ||
public IDisposable CancellationRegistration; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This property isn't used yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clairvoyant? Removed...
e6ca887
to
d2b7918
Compare
Failure as |
d2b7918
to
fa8fe3d
Compare
Yeah. It might be a while until the packages on the aspnetcidev feed are updated. A lot of our builds are failing on our internal ci due to the transition from dnx to dotnet/cli. Until then you can change your nuget.config to reference the aspnetvolatiledev feed. That doesn't help with travis/appveyor though 😢 Blame @BrennanConroy 😛 |
Thanks! |
Resolves waiting issues observed while investigating #572
Also resolves sync-waiting issues observed in #565 (but not the connection issues #567 deals with)
Resolves #590