http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Try rebooting your machine and running the test, or force paging your memory to disk, bet the first call to the service is "significantly" slower... According to Microsoft this is expected behavior. ;) http://ayende.com/3378/nmemcached-a-wcf-experiment#comment10http://ayende.com/3378/nmemcached-a-wcf-experiment#comment10Wed, 25 Jun 2008 22:32:23 GMTThis is becoming an experiment on tuning WCF services. :) http://ayende.com/3378/nmemcached-a-wcf-experiment#comment9http://ayende.com/3378/nmemcached-a-wcf-experiment#comment9Wed, 25 Jun 2008 21:02:14 GMTAfter disabling reliable sesisons, I am down to ~6100ms http://ayende.com/3378/nmemcached-a-wcf-experiment#comment8http://ayende.com/3378/nmemcached-a-wcf-experiment#comment8Wed, 25 Jun 2008 20:46:49 GMTAlso, disabling reliable sessions might help a bit as well, unless you explicitly need them... http://ayende.com/3378/nmemcached-a-wcf-experiment#comment7http://ayende.com/3378/nmemcached-a-wcf-experiment#comment7Wed, 25 Jun 2008 20:31:28 GMTIn that case you're probably already using the binary encoders. I'm not sure exactly how your nmemcached architecture works, but it;s possible you might get away with some interesting things using the peer channels instead. http://ayende.com/3378/nmemcached-a-wcf-experiment#comment6http://ayende.com/3378/nmemcached-a-wcf-experiment#comment6Wed, 25 Jun 2008 20:28:57 GMTTroy, Haven't seen that, thanks. Just tried this, and this and removing security dropped to 6454ms http://ayende.com/3378/nmemcached-a-wcf-experiment#comment5http://ayende.com/3378/nmemcached-a-wcf-experiment#comment5Wed, 25 Jun 2008 20:26:41 GMTI am using new NetTcpBinding(), whatever that means http://ayende.com/3378/nmemcached-a-wcf-experiment#comment4http://ayende.com/3378/nmemcached-a-wcf-experiment#comment4Wed, 25 Jun 2008 20:16:54 GMTJust some quick test on my machine - and I did not see your original code and whether you have security in there or not. netTcpBinding ============= created clients, starting to connect read 10000 wrote 10000 took 4752 total 10005 reads and 10002 writes using 20 connections netTcpBinding - w/o security ============================ created clients, starting to connect wrote 10000 read 10000 took 3816 total 10001 reads and 10003 writes using 20 connections http://ayende.com/3378/nmemcached-a-wcf-experiment#comment3http://ayende.com/3378/nmemcached-a-wcf-experiment#comment3Wed, 25 Jun 2008 20:09:26 GMTYou've probably already seen this, but sending it just in case. http://blogs.msdn.com/wenlong/archive/2007/10/27/performance-improvement-of-wcf-client-proxy-creation-and-best-practices.aspx I know that in .NET 3.0, calling client.Open() explicitly before making the service call was another way of speeding up performance. I don't know if this makes a difference in .NET 3.5. http://ayende.com/3378/nmemcached-a-wcf-experiment#comment2http://ayende.com/3378/nmemcached-a-wcf-experiment#comment2Wed, 25 Jun 2008 19:19:50 GMTHaven't looked at the code, but out of curiosity: Are you using the binary or the text encoders?. http://ayende.com/3378/nmemcached-a-wcf-experiment#comment1http://ayende.com/3378/nmemcached-a-wcf-experiment#comment1Wed, 25 Jun 2008 18:50:10 GMT