We have been running some performance profiling tools in our Umbraco solution. We are running a lot of traffic across our websites.
What has been highlighted as Hot Spots by dotTrace, ANTS Performance and also JustTrace is Umbraco.Core.Logging.ParallelForwardingAppender.SubscriberLoop.
I'd like to know why this is being highlighted by all the profilers and wondered if there was a quick answer to this before I go and dive into the source code and see what it is doing.
I know this is an async appender but this is taking resources on the server and wondered about removing this appender.
It's because this method uses a BlockingCollection.GetConsumingEnumerable to read the queue of messages it needs to process on it's own thread. So yes, if there are no other high consuming CPU threads, this will show up since it's blocking.
Umbraco Logging - ParallelForwardingAppender.SubscriberLoop - Performance?
We have been running some performance profiling tools in our Umbraco solution. We are running a lot of traffic across our websites.
What has been highlighted as Hot Spots by dotTrace, ANTS Performance and also JustTrace is Umbraco.Core.Logging.ParallelForwardingAppender.SubscriberLoop.
I'd like to know why this is being highlighted by all the profilers and wondered if there was a quick answer to this before I go and dive into the source code and see what it is doing.
I know this is an async appender but this is taking resources on the server and wondered about removing this appender.
Anyone with knowledge around this?
Hi Aaron,
Did you get anywhere with this issue? I am seeing similar issues.
Thanks
Barry
It's because this method uses a BlockingCollection.GetConsumingEnumerable to read the queue of messages it needs to process on it's own thread. So yes, if there are no other high consuming CPU threads, this will show up since it's blocking.
More info: https://stackoverflow.com/a/5356271/694494
is working on a reply...