Search Indexer with virtual size of 250,000 K

[Wowbagger]

Running Windows XP Pro, SP2 on a machine with 1Gb RAM

Windows Task Manager shows 48 processes with a commit charge consistently
above 500M / 2460 M. According to Windows Task Manager WindowsSearch.exe
uses 5M of RAM with a VM size of just under 10M and searchindexer.exe using
32M / 42M - but when I use process explorer searchindexer.exe has a virtual
size (in this instant) 275,244 K - about 2/3 as large as the process with
the next highest virtual size (explorer.exe) and twice as large as
svchost.exe?

 

[Dennis McCunney]

Running Windows XP Pro, SP2 on a machine with 1Gb RAM

Same here.

Windows Task Manager shows 48 processes with a commit charge consistently
above 500M / 2460 M. According to Windows Task Manager WindowsSearch.exe
uses 5M of RAM with a VM size of just under 10M and searchindexer.exe using
32M / 42M - but when I use process explorer searchindexer.exe has a virtual
size (in this instant) 275,244 K - about 2/3 as large as the process with
the next highest virtual size (explorer.exe) and twice as large as
svchost.exe?

Yes. So?

In Process Explorer, Virtual Size is the total of used RAM plus swap
space for the process. Working Set is a much closer figure for what the
process is doing at that moment.

Personally, I turn Windows Indexing *off* to avoid the overhead. I use
a free, open source product called Locate32 to create a searchable hard
drive index. It's exceptionally fast, and can be set up to do scheduled
updates of the index at convenient times. Go here:
http://locate32.webhop.org/

To locate content *in* files, I use Google Desktop, though there are
other solutions for that as well.
______
Dennis




--
"The heights by great men reached and kept
Are not obtained by sudden flight
But they while their companions slept
Went toiling upward through the night"

-- Longfellow