Well, right now we are testing just running our load-balancer with "session affinity" so that once a user makes a request and is "round-robined" to a web front-end server, they "stick" to that server so their session remains in proc on the server they "stick" to.  This way we don't have to share session state.  However, if your experience tells you that DNN doesn't behave well in this scenario (with session affinity on load-balancer), please feel free to share your experiences and or opinions. 

Thanks for the feedback!

-- W.G.

 Hello Will,

Just been reading your thread from last year, how is the system working for you now?  Was is performance you were striving for or redundancy.  How have both been.  

From a performance  perspective, how does your DNN environment compare to a standalone machine ?

thanks for enjoyable reading,

Mark Breen

Ireland