logo

Pages


Erick’s Games

Faith

Older Games

Other Blogs

Posts

Categories

 

April 2009
S M T W T F S
« Mar   May »
 1234
567891011
12131415161718
19202122232425
2627282930  



Comments

Administration

Searchindexer.exe -> Taking up too much memory Windows XP

April 2, 2009

I don’t know about you, but I use and abuse my computer until it can barely perform, and then I still refuse to reboot the thing.  Because of this, after the computer has been on for about a month or so, you begin to notice all the processes that take up resources and try to optimize the resources to cut down on memory leaks.  I mean, if it isn’t for the memory leak, the computer can stay on for years instead of months.  The one thing that always bothered me was SearchIndexer.exe and why it always consumed so much RAM.  This morning, I check and it is taking 400k of memory.

Why?

I’m glad you asked.  The reason being is that SearchIndexer is Windows Desktop Search utility that is supposed to perform better than Google Desktop.  Due to my huge email size and amount of emails I receive, it takes up a lot of resources to index it and perform faster searches.

Lets think about that for a second.  The Windows Desktop Search is supposed to make my searches and windows experience better, by making my computer run slower?  This just cannot be the Microsoft way.  Once I realized what this utility does and how it is not appropriate for my usage (I may use the search utility 1 or 2 times a year, if I’m lucky) I decided to give it the axe.

Here are the directions on how to remove the Windows Desktop Search

Go to add/remove utilities

Remove Windows Desktop Search

The end…simple right?  Oh Microsoft and their silly ways.  To be fair, I hate google desktop too.  I don’t know why people can’t just remember where they put their documents or emails… :)

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • Technorati

6 Responses to “Searchindexer.exe -> Taking up too much memory Windows XP”

  1. 1
    dougNo Gravatar Says:

    I have thousands of data files spread across several hard drives and a 2gig OST outlook inbox on my pc.. I use wds all the time and appreciate it’s ability to find pieces of data.

    If you want to use search and find data, you have to give up a little ram and processing to rebuild the index.. jeanne doesn’t just fold her arms and blink and voila it’s found!

    You’re probably the same person who complains about resturant service and cuts in line on the freeway onramp..

  2. 2
    KoopaNo Gravatar Says:

    Doug,

    I started my post with, I never use the windows desktop search therefore, do not need to have the thing sucking the life of my computer. You use it, great for you. I wouldn’t advise you to get rid of it then.

    The point being is, I DON’T want to use search and find data! I only store documents in a few locations and don’t really to search for anything.

    The end, if you use it, keep it. If you don’t use it (like me) get rid of the fucking thing because it is a memory whore. My computer has ran much better since it has been gone!

  3. 3
    dougNo Gravatar Says:

    my apologies.. it get it now.. you are entirely right. I now feel like an idiot.

    My searchindexer service was at 10mb!

  4. 4
    KoopaNo Gravatar Says:

    Yeah, it may have also been an issue that has been fixed in a windows service pack as well. I only apply the hotfixes that deal with security issues and I hate doing it because it interferes with my up time!

  5. 5
    VistaX64No Gravatar Says:

    I was just searching for some information on this topic and found your page. With Vista running my SearchIndexer.exe is taking up a little over 100 MB I also never use it. So wasteful.

  6. 6
    Chris BachNo Gravatar Says:

    i run Windows XP Home Edition 5.1 and can not find searchindexer.exe in my processes nor is it anwhere in my add/remove windows components.

    perhaps a patch took care of it or maybe its been renamed? i see a services.exe but it’s running like 2,500k in the background.

    any suggestions? i severely dislike memory hogs.

    thanks

Leave a Reply

Google