I'd start with testing the easiest points first, the actual service and the components behind it.
Rig up an application to hit these points in a multi threaded fashion. Eg. In a loop x long, create a new thread and fire off a call to svc or method. Repeat y times with z interval. Grant On 25/01/2012 4:38 PM, "Greg Keogh" <[email protected]> wrote: > Some potential customers have asked if our product has been stress tested. > The answer is that we’re not telling them until we figure out if it’s > possible. Web searches produce lots of hits on this subject, but I thought > it would be wise to ask here first to see if anyone has experience and > advice.**** > > ** ** > > Our app is actually composed of a Silverlight 4 app in the browser client, > a C++ COM component at the other, and a WCF service to allow the two to > talk to each other via XML. So there are many potential points for > performance trouble: Loading the SL app, rendering complex graphics in the > SL app, transmitting XML (it’s zipped), network speed, IIS performance, and > performance of the C++ component which further talks to the file system and > contacts a master authentication server using FTP. The author the C++ > component says it was not written with multithreading in mind.**** > > ** ** > > So we have to think of a way of stress testing this conglomeration. I’ll > continue reading web search results in the meantime.**** > > ** ** > > Greg**** >
