Click here to get back home

desktop search memory footprint

 HomeNewsGroups | Search | About
 microsoft.public.msn.search    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
desktop search memory footprint Stephen 05-16-2005
Get Chitika Premium
Posted by Stephen on May 16, 2005, 5:31 pm
Please log in for more thread options


my overall view is that this is very impressive, certainly an improvement
over past beta versions.

My only concern is the memory footprint. It seems that
'windowssearchindexer.exe' takes up around 55MB of memory for quite a lot of
the time. It just seems a lot 'heavier' than previous versions.

Is anybody else experiencing this?


Posted by Joel Moore on May 16, 2005, 9:46 pm
Please log in for more thread options



> my overall view is that this is very impressive, certainly an
> improvement over past beta versions.
>
> My only concern is the memory footprint. It seems that
> 'windowssearchindexer.exe' takes up around 55MB of memory for quite a
> lot of the time. It just seems a lot 'heavier' than previous
> versions.
>
> Is anybody else experiencing this?

Yes. Mine's taking up 67 MB of virtual memory. Seems excessive.

I'm just trying out MSN DS after using Google's DS for a while now. For
the most part MS seems like a better product but I can't afford to
sacrifice this much memory.


Posted by jonathanh [MSFT] on May 16, 2005, 10:34 pm
Please log in for more thread options


Virtual memory size tells you how much memory the process would occupy *if*
it all had to be present in RAM at once. But MSN DS has been coded so that
its working set - the portion of the process that is always present in RAM -
is a lot lower than its VM size. Use the "Memory Usage" column in task
manager to see the working sets of every process on your system.

For example, on this laptop WindowsSearchIndexer has a VM Size of 66 MB, but
a memory usage of only 8 MB. It's the second figure that will have far more
of an impact on your everyday computing experience.

Joel Moore wrote:

>
> > my overall view is that this is very impressive, certainly an
> > improvement over past beta versions.
> >
> > My only concern is the memory footprint. It seems that
> > 'windowssearchindexer.exe' takes up around 55MB of memory for quite a
> > lot of the time. It just seems a lot 'heavier' than previous
> > versions.
> >
> > Is anybody else experiencing this?
>
> Yes. Mine's taking up 67 MB of virtual memory. Seems excessive.
>
> I'm just trying out MSN DS after using Google's DS for a while now. For
> the most part MS seems like a better product but I can't afford to
> sacrifice this much memory.
>


Similar ThreadsPosted
memory could not be read October 16, 2005, 5:46 am
The memory could not be "read". October 7, 2005, 12:33 am
Tabbed Browsing and excessive memory usage December 14, 2005, 11:33 am
Acrobat Reader Process Stays in Memory April 3, 2006, 3:47 pm
Large Index crashes machine (memory leak, handle leak?) May 25, 2005, 4:33 am
Windows Desktop Search or MSN Desktop Search November 14, 2005, 12:59 am
Hard to search the web with long search string after desktop deskbar search. June 3, 2005, 3:19 pm
Desktop Search starts, but won't open the search window or index f June 16, 2005, 9:22 pm
Use MSN Desktop Search API to search Exchange Emails and Appointments July 22, 2005, 10:54 am
HOWTO: Add new search "locations" to Windows Desktop Search August 2, 2005, 2:17 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap