Someone recently asked about how to load test WCF – apart from the usual things like LoadRunner, VSTS Test Load Agent, etc a couple of other interesting options came up. One is WCF Load Test and the other JMeter. WCF Load Test generates a unit test taking in data from a a trace file along with the relevant WCF proxy or interface.
I must admit, JMeter would not have been one of the things that would have come to mind to me in this context, but technically there is nothing stopping from you using it as you can stress and load test any http request.
Similar posts to check out:
- July 7, 2011 -- Automatic eTag Management with WCF Web API Message Handlers (0)
... - May 26, 2011 -- Troubleshooting WCF Performance – Part 1 (0)
More related details on Dustin's post - WCF scales up slowly with bursts of work.... - September 21, 2008 -- Avoid using “using()” (0)
The using statement in C#, seems to be quite useful especially to a developer as theoretically, you not have to do anything to release any memory you might have used and the CLR automatically frees up this memory for you.
However, over time, I have had so many issues with it and subtle problems (in certain situations) I am starting to avoid it now.
The two best examples that I can think of are database connection pools and WCF connections. You might think that a “using” statement would clo...
Tags: .wcf
