Azure Redis Memory Usage (w3wp.exe dump) Insight
<p>Can anyone tell me if the type of behavior outlined in the memory dump from Visual Studio <a href="https://i.stack.imgur.com/8ackz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8ackz.png" alt="w3wp dump output"></a></p>

<p>Is normal? for instance does the StackExchange.Redis.PhysicalConnection run that high on inclusive size (bytes)? Or is that really high?</p>

<p>Basically we are experiencing slowness with our web head after converting our code to run on Azure Redis from Session (we are now serializing and deserializing as needed and storing in Redis cache) but overall performance is horrible.</p>

<p>The requests complete but it can take a while, is that due to the single threaded nature of Redis? We are using the configuration outlined as best practice by the Azure Redis team as outlined here <a href="https://stackoverflow.com/a/28821220">https://stackoverflow.com/a/28821220</a></p>

<p>What else can we look at to help increase the performance as the current performance is not acceptable as a viable replacement for our session based implementation (asp.net webforms/sql server/azure IaaS) we currently have.</p>

<p>PS - Serialization and Deserialization does cause a hit, we understand that IIS spoiled us with its own special memory pool for non-serialized datasets and such, but there is no way that it should cause a 300-500% increase in page loads like it is now for us.</p>

<p>Thoughts appreciated!</p>

<p><strong>@Tim Wieman</strong></p>

<p><strong>How large are your cached objects?</strong> 
They can range in size, there are some datasets stored in redis.</p>

<p><strong>What type of objects are they?</strong> 
Most objects are custom objects w/variable number of properties, some even contain collections.</p>

<p><strong>What serializer are you using?</strong>
We are using Newtonsoft for anything that doesn't require Rowstate and the required binary serializer for the datasets that do need rowstate.</p>

<p>All serialization, and subsequent deserialization, is done in code before call redis databases StringGet or StringSet.</p>