On Wednesday 11 June 2008 01:18:40 you wrote:
My impression is that it looks all of the time and never ever stops when an initial index has been built even when there have been no further changes.
That is definitely not the case, at least with the version on 11.0. I am pretty confident about that. After initial indexing is over, there should be no activity.
- dBera
PS: There was a corner case in the versions in 10.x and earlier which caused endless crawling like you said but that was fixed long ago.
I posted a comment on the kde list much the same as the one I made here plus the fact that I was left with the feeling that it was operating too far up the software tree and that it was a very ambitious project. Wondoze seems to offer indexing via very low level software eg as an extension near the bottom of the file storeage tree. I don't see how it could ever be efficient unless it's done that way. No responce other than "interesting " from good old kevin. I had it running with about 8gig on my desktop over several thousand files. It was still chuntering away after several days despite no use over night. On memory useage I wasn't bothered as even 10.1 seems to use all available memory even without beagle. That's good as I see it. I still had excellent file system i/o rates. On 10.3 86_64 for these are held to over a 1gig of data. Beagle was definitely wrecking disc access time one way or the other. Freeing memory or disc access. This is why I feel that the mechanisms may be too high up in the software tree. CPU useage is all so irrelevant providing it gets out of the way quickly enough. Maybe it tries to save what it's done rather than just ditching the lot. Who knows. On my general feeling - only used it a couple of times - From memory there weren't any easy user level filters - eg File name, contents, system, desktop, remote file, web, file type etc. Speed wise at that level I was initially impressed but some seemed to take a fair while. Much quicker than Ksearch however. The version of beagle I used was on the suse 10.3 download. If it's bugged why haven't I been offered an update? If the developers want their code to be used and liked they need to make sure this happens. It just means more space needed on the suse mirrors which shouldn't be a big deal. No doubt they might not like the extra traffic. John -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org