|
From: | Philippe Roussel |
Subject: | Re: GWorkspace mdextractor problem |
Date: | Sat, 10 Feb 2007 12:02:48 +0100 |
User-agent: | GNUMail (Version 1.2.0) |
On 2007-02-10 01:30:13 +0100 Enrico Sersale <enrico@fibernet.ro> 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 mdextractorIs 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
And on a close enough topic : will MDFinder.app replace GWorkspace actual search tool ?Perhaps, in the future; for the moment it is a new thing that, besides a good name for all the stuff and some icons, needs to be used and tested by the GWorkspace users.
--The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell. - St. Augustine
[Prev in Thread] | Current Thread | [Next in Thread] |