If you follow my blog much, then you know performance is a bit of an interest of mine. Well here’s one that pretty much pulls the pants down on the CF loader. Nothing like a 3 second load time for some classes. Admittedly it’s an edge case and there seems to be some wacky logic in the repro code, but it’s still pretty interesting. And kudos to Noah for looking into it, finding the problem and at least explaining why it’s happening and how to mitigate it at least to a degree (and to his managers for letting him do it). Without doubt the CF team is the most transparent team I’ve encountered at Microsoft. They readily admit where they’ve got shorcomings and are happy to explain why we see problems. One can only hope this practice continues.
