Lately, I´ve been working some with performance testing and opposite to what I think most performance-gurus would like I´ve ended up writing my own tools for this. Yes I know I´m reinventing the wheel but the way our services are build I think this is easier.

Anyway, what I wanted to share is a way to allow a client multiple concurrent calls. Starting these projects I thought – Well I´ll just thread out and make my calls. Turns out it´s not as simple, you need to configure .Net to allow multiple concurrent connections in the lower tiers of the framework. Fortunately this is really simple, just put this in your configuration and you are ready to roll:

<system.net>
  <connectionManagement>
    <add address="*" maxconnection="100"/>
  </connectionManagement>
</system.net>
Why not join the newsletter?

Why not join the newsletter?

If you're not a fan of facebook or twitter, sign up to the newsletter and I'll send you a quick update every so often with what's going on and new posts coming out.

You have Successfully Subscribed!