Gex
Oralapostel
|
ich habe diese vier files (siehe attachment) auf jeder meiner drei partitionen was machen die da, wo kommen sie her, werden sie gebraucht oder kann ich sie löschen? die nerven mich nämlich irgendwie
|
Gex
Oralapostel
|
argh attachment vergessn
ffastun_7320.jpg (downloaded 49x)
|
MadDoc
MadDoc
|
Find Fast
Find Fast is installed as a part of Microsoft Office. Starting with Office 2000, the default is not enabled, however, with previous versions, it is enabled. On a brand new, never before used NT 4.0 SP3 system with an empty D-drive, FastFind placed the following files
ffastun.ffa 4,109 ffastun.ffl 8,192 ffastun.ffo 4,096 ffastun0.ffx 4,096
total 20,493 bytes
And after copying about 12,200 files (~350Mb) to the D-drive and waiting over night ffastun.ffa 4,379 ffastun.ffl 131,072 ffastun.ffo 57,344 ffastun0.ffx 327,680
total 520,475 bytes
Find Fast is run via Start / Programs / Startup. This parasite causes lots of disk activity whenever no one is using the machine. While it may speed up some searches, there is little documentation explaining what it does. (See Overview of Find Fast Indexer for some details.) It is my observation that it frequently activates the hard drive and slows down overall system performance.
When you first boot your system, this parasite is dorment, merely consuming memory but not using a lot of CPU time. After a while, it wakes up using about 50% of the availble processor capacity. (So far, this is not unlike a screen saver which stays in the background until the timer triggers.) However, unlike the screen saver which goes back to sleep, once this parasite is active, it stays active until you re-boot the system.
On an NT 4 system, right click the Task Bar and select Task Manager. On my NT 4 system, under Processes there are 2 instances of FindFast.exe! Currently, my processor indicates that it has been 27 hours since the last re-boot, and 1.5 hours have been used by FindFast.exe! This means that 5.5% of the computer's bandwidth is being wasted by this parasite. In addition, the hard drive is being accessed a little faster than once a second.
I killed it with the End Process button. Now the hard drive is quite.
-------------------------------------------------------------------------------- Some additional data - I booted the NT 4 system on Friday and left it running all weekend. The following Monday and Wednesday morning numbers are from the Task Manager. Program Mon Wed System Idle Process 34:42 59:28 FINDFAST.EXE 32:36 57:33 FINDFAST.EXE 0:00 0:00 System 0:42 1:14 TASKMGR.EXE 2:22 5:52 explorer.exe 0:46 1:39
Yes, there are 2 instances of findfast. Together, they consume about 6.3 Meg of memory! This system currently has 64 Meg of memory and is using about 40 Meg. Imagine if I had only 32 Meg of RAM how much thrashing there would be.
Over several days of observation, 2 of which are shown above, the findfast CPU Time stayed approximately 2 hours behind the System Idle Process. I assume that this is approximately how long the system was on before findfast activated and that afterwards findfast consumed about 50% of the available CPU time.
Bearbeitet von MadDoc am 24.04.2002, 13:48
|
HVG
untitled
|
m$ fast find file nehm an des is so a friggin "index" damit es suchn schneller geht btw: sowas kann manchmal helfn EDIT: wow gut gratn
Bearbeitet von HVG am 24.04.2002, 13:48
|