I have been running with a 256GB Crucial C300 in my Lenovo W520 for a while now and it has been great. I love the performance and I love to see applications pop (vs poop) open. Someone, I forget who, tweeted the other day about a great deal on Amazon on a Crucial M4 for $399 so I hit Amazon, did the 2 day Amazon Prime ship and here I sit with a new drive just populated with Acronis True Image Home 2011.
So have you ever heard this “There is Nothing in the ULS Logs” or better (worse) yet you have experienced it. Yea me too, it’s a real bummer and your next step is to typically crank up the ULS logging verbosity and crossing your fingers. Sometimes you get lucky and sometimes you don’t, so where next? I have found myself attaching a debugger and looking at the managed exception messages that trail across the debugger window while I reproduce the problem and sometimes these are enough to either provide a line of investigation or possibly the answer to my issue.
As a follow up to my earlier post Making Debugging a SNAP I would like to share with you a new feature I added recently which allows you to monitor exceptions within your managed processes. The exceptions we are talking about here are managed exceptions. Typically you want to see exceptions treated as exceptional, that is, you don’t want to throw exceptions to determine flow control within a normal execution path. You really want exceptions to be exceptional, that is, something which has occurred and you did not expect and most likely do not desire. For .Net processes entering a try/catch is relatively cheap when it comes to performance but throwing an exception can be expensive. A process which throws a large number of exceptions during a normal run will have degraded performance. As each exception is thrown the exception record must be built which includes a walk of the stack and all the frames within a thread which can be relatively expensive, especially if you have very large stacks.
Continue reading “Monitoring Exceptions is a SNAP”
I am working on a MVC4 RC application within the Visual Studio 2012 RC. I started to notice my web pages were starting to get a bit sluggish with regard to response times. I found that I could not get any page to return in less than 1 second. So I stated to do a bit of digging â€“ I created a TestController controller with a single Index() action and a view which did not use any master page/layout. The page, according to FireBug was 2-3ms coming from IISExpress running on my local dev machine. Now the view was a very simple page with a DocType, header, and body without any content so this is about as basic as you can get.