On 2007-02-10 13:02:48 +0200 Philippe Roussel <[EMAIL PROTECTED]> wrote:
On 2007-02-10 01:30:13 +0100 Enrico Sersale <[EMAIL PROTECTED]> wrote:
The problem is that mdextrator seems to be a cpu and memory hog :
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME COMMAND
30304 philou 25 0 172m 22m 7876 R 86.8 1.5 6:13 mdextractor
Is this normal, should I wait longer for mdextractor to finish its work ?
The first time you run mdextractor it needs to create its database; this
means that it must extract the contents of all the indexable directories
(default your home directory and the GNUstep Applications, Headers and
Docomentation directories). This can take some time...
When the database is created, all the successive work of keeping it updated
is not cpu intensive.
Well I thought about that and let it run. I don't have that much data :
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME COMMAND
30304 philou 25 0 172m 22m 7928 R 93.8 1.5 622:48 mdextractor
Do you mean that 93.8% is *after* the first indexing?
It should look something like this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27821 root 16 0 55200 38m 8516 S 0 3.8 2:19.95 mdextractor
and I, for texting, let mdextractor index 9743 directories containing 80245
indexable paths and 869200 unique words!
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
