Linked by Thom Holwerda on Thu 28th Jun 2007 18:32 UTC, submitted by Beffidile
Thread beginning with comment 251591
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Need to move away from batch indexing
by metaph3r on Fri 29th Jun 2007 13:20
in reply to "Need to move away from batch indexing"
The current Linux indexers Beagle, tracker and Google Desktop, relies on batch indexing by a running process. While this is fine for initial indexing, it is slow and the index is outdated as soon as someone creates a new file or changes an old one.
This is not true. At least Beagle also index changes as soon as they appear. It is informed by the inotify facility of the linux kernel about filesystem changes.
RE[2]: Need to move away from batch indexing
by elsewhere on Fri 29th Jun 2007 14:40
in reply to "RE: Need to move away from batch indexing"
This is not true. At least Beagle also index changes as soon as they appear. It is informed by the inotify facility of the linux kernel about filesystem changes.
I think that's reasonably true for every search utility now outside of locate and find-utils. None of them are doing batch updates as part of a cron job anymore.




Member since:
2006-11-21
The current Linux indexers Beagle, tracker and Google Desktop, relies on batch indexing by a running process. While this is fine for initial indexing, it is slow and the index is outdated as soon as someone creates a new file or changes an old one.
In spotlight for MacOS on the other hand the index gets automatically updated as soon as a file gets changed. If you open a Spotlight search for "Foo" and go to a terminal and type 'echo "foo" > test.txt', the search window will update to include test.txt immediately.
The same should happen with Beagle and Tracker. As an added bonus, you wouldn't have to have the indexer search through your file system so often to find updates.