René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Synchronous Task.WaitAll() in LoqQueue causes async/await performance problems in .NET Core","articleBody":"I have an Azure function app that's performance-critical. After instrumenting it with NLog and a StackifyTarget with an AsyncWrapper, I was perplexed to be observing the following:\r\n![stackify logging](https://user-images.githubusercontent.com/8496021/53379439-86427e80-3937-11e9-8e6f-e3cf3a9a022c.JPG)\r\n\r\nAs you can see, a request that I would have expected to execute in 20ms instead took 775ms (39x longer!) due to what looks like blocking code from the StackifyTarget. Thinking perhaps the NLog AsyncWrapper wasn't behaving as it should, I did some debugging and found that the wrapper itself is behaving as expected.\r\n\r\nDigging deeper, I found that the AsyncWrapper is pretty useless when used in conjunction with the StackifyTarget, as the StackifyTarget itself queues messages up for \"asynchronous\" uploading using [System.Threading.Timer](https://github.com/stackify/stackify-api-dotnet/blob/f04e9f12d61504dbc9dec7a66a7e8cbbc1f86058/CoreSrc/StackifyLib/Internal/Logs/LogQueue.cs#L52).\r\n\r\nThis would be great _if_ the timer function was actually asynchronous. [It's not.](https://github.com/stackify/stackify-api-dotnet/blob/f04e9f12d61504dbc9dec7a66a7e8cbbc1f86058/CoreSrc/StackifyLib/Internal/Logs/LogQueue.cs#L324)\r\n\r\nMy code, which uses async/await code for all I/O operations, is now sharing a threadpool with a synchronous, I/O-bound resource hog.","author":{"url":"https://github.com/AdamEssenmacher","@type":"Person","name":"AdamEssenmacher"},"datePublished":"2019-02-26T01:27:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/84/stackify-api-dotnet/issues/84"}