running better now. This was triggered it seems by me checking an ASP.NET 3.0 WCF setting on a site, or purely coincidence, I did not make any changes was just looking the settings. We have on occasion had asp.net change trigger the need for an iisreset but it doesn't normally happen like this, and no change was made.