Ok, sometimes i regret having windows vista 64Bit on my development machine. An today was such a day. I tried to set up a web stress environment for our new web portal.
I tried several great tools like OpenSTA and WebLoad to run on my Windows Vista, but nothing worked. The i downloaded quite angry the good old Web Application Stress tool from Microsoft and run it as admin. And it works.
Our new Portal has its business logic on a .NET based windows service, so i want to test interprocess communication via WCF and a named pipes channel. The WAS tool works great for this and i could tune my IPC to get a throughput of about 80 pages per second. I think this isn't so bad for WCF. But i try to become better.
Addition:
I've used a channel pool for my wcf channels ad come now to 1000 / pages per second. A roundtrip of a simple function ( bool Test(bool foo ); ) need about 50uS on a named pipes channel. The processing of the on the IIS takes much longer. For now the things have become right. I can place the business logic on the app server and get a killer throughput because of efficient caching. This is the way i like web applications.
Showing posts with label connection pooling wcf named pipes. Show all posts
Showing posts with label connection pooling wcf named pipes. Show all posts
Thursday, January 22, 2009
Subscribe to:
Posts (Atom)
Posts
