Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It's possible that what you're seeing is just caused by Beagle going off an indexing everything it can find on your computer. Once it has built its initial database then keeping it up to date takes far fewer resources.

    I just let it run overnight.
    • I suppose that is a "feature" to have to let it hog your system while it indexes? I for one would want to use my system once I built it and not have to wait for something to do an index before having normal performance.

      • How is this anything new? You’ve heard of updatedb?

        • Not the same. An indexing system like Beagle looks at the content, not just the name and location. However, in most instances locate is my first choice anyway ;)

          • It is the same, in that it hogs your disk and a sizable amount of CPU (though not quite as much of that). updatedb just gets done a lot sooner because it scans a lot less data (just the filenames, not the content). It doesn’t seems unreasonable to me to simply relegate the full scan to the wee hours.

    • This was after installing it and leaving it over 2 weekends and a weeks holiday! I could understand the indexing taking a few hours, but after 9 days it really should have completed that. I don't have that many files in the 20GB used on a 40GB drive.

      On this particular machine, Beagle isn't something that would be particularly useful anyway, so would have been an unwanted overhead. The fact that it didn't seem to cope very well, just meant I got rid of it sooner rather than later.