Windows Desktop Search

Yesterday, I decided to install Windows Desktop Search yesterday. Just for kicks. I thought they might have changed fixed things by now.

I just thought I’d post a little note about my results. I, of course, restricted what it can index to only my personal folders and my Outlook PST file (about 65 MB). (I also disabled Google Desktop for the tests.) After allowing it to perform a complete index of my system, I let it run normally.

It seemed okay. Search results came back very quickly. No problems so far.

Well, today, I tried compiling my current project. I noticed very quickly how un-quick it was compiling.

In other words, I know very well how long this compilation takes. It has been my standard for testing the performance of my home-built dual QuadCore workstation against my (amazingly fast) Gateway MP8708 laptop. See The Test and its update for details about my VS2005 web solution that I use as a standard for testing machines.

Sucks, don’t it!?

Let’s see that is 2 minutes and 7 seconds, compared to 7 minutes and 44 seconds. Ouch, that isn’t good at all.

One thing to note also is that the source code is not located within the folders I explicitly defined for WDS to index. Now, isn’t that interesting!?

Normally, I would go and try to figure out why this is happening to provide a solution to the problem for others… But, I just un-installed it instead. As for the solution? Install Google Desktop Search.

For those curious why my laptop compiles faster than my dual QuadCore system, see Gateway MP8708 laptop vs. Dual Intel QuadCore. It’s all good.