Geeks With Blogs
Chris Falter .NET Design and Best Practices August 2006 Entries
Visual Studio Team Server, the Gangly Adolescent
As a high school sophomore I was 6'1“ tall and 140 pounds--a human bean pole. My arms shot out of my sleeves like beanstalks in Jack's garden. You could practically see my ankles emerging from the bottom of blue jeans as I stood before you. As a physical specimen, though, you could see on my frame what I would eventually become as an adult, after a little more maturation. I was a gangly adolescent. I'm almost delirious that Microsoft finally released Visual Studio Team Server (VSTS), especially ......

Posted On Thursday, August 24, 2006 11:44 PM

Solved: The Mystery of DataView's Poor Performance with Large Recordsets
Well, maybe I solved it. At least I have a reasonable hypothesis. Reader “Ghassan” postulated in a comment to my earlier post that it's the extra burden of creating an array of DataRowView that puts the DataView approach at a disadvantage to DataTable.Select. However, a glance at DataView's default indexer in Lutz Roeder's wonderful Reflector utility shows that the array of DataRowView is not created while the constructor is executing. Instead, it is created when and if the DataView indexer ......

Posted On Tuesday, August 15, 2006 6:24 PM

Why You Might Prefer a DataView to an Array of DataRecord
Before we get too obsessed about the performance advantages of an array of DataRecord over a DataView, let's remember that a DataView behaves differently than an array of DataRecord. No matter how you modify the data in an array of DataRecord, the array bounds will always be the same. However, modifying a field in a DataRecord may cause it to disappear from a DataView, if the modification causes the record to be filtered by the DataView.Filter property. Or if you modify a DataRecord in a DataTable, ......

Posted On Monday, August 7, 2006 7:47 PM

Array of DataRecord vs. DataView: A Dramatic Difference in Performance
I spent much of last weekend running tests against a table with 122,000 records. The folks at Citibank and Geico would just yawn at that amount of data, but where I work that's fairly heavy lifting. As I was tuning and validating the tests, I used a bit-field flag ("TestCompleted") to track whether a record had already been tested. No need to do work twice, eh? Because this was a one-time set of tests, I used a TableAdapter (the simplest possible code) to grab all the records, then I needed to filter ......

Posted On Friday, August 4, 2006 6:34 PM

Copyright © Chris Falter | Powered by: