Bill Roper (billroper) wrote,
Bill Roper
billroper

Hopelessly Bad

Some time ago, the folks in charge of our web interface decided that we should return data as a .NET DataSet. This may not have been the happiest choice.

Apparently, the indexing in the .NET DataSets is badly broken. I'm trying to do a Select on two columns to retrieve -- in the desired order! -- the 7400 points that are defined as rows in a particular DataSet. The columns are both primary sort keys.

This takes 25 seconds or so to run. If I comment out the Select statement, it takes less than a second to complete the loop.

Supposedly you can do the query against the contained DataRowCollection instead of against the DataTable and that will be faster. It isn't.

Supposedly you can force the table to create an index for a column and it will be faster. That might be true, but doesn't work when you need to search on more than one column.

Overall, this is so broken it isn't even funny.

I think I'll go to England.
Tags: filk, musings, work
Subscribe

Recent Posts from This Journal

  • Time for Rebuilding

    Well, there's nothing like research. Having determined that DDR5 is going to carry a substantial price premium over DDR4 memory for at least a year…

  • Driven Wild

    The studio computer continues to misbehave in various ways. When I fired up Cubase today, I got a lot of nasty, blocky video, despite having cleaned…

  • Some Old Doggerel

    I recall having mangled a CSN tune many years ago on the way to Contraption. Like that convention, the particular co-worker whose code I was digging…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 1 comment