Each time the Beagle indexing is kicking in (usually within 5-10 minutes since I turn on my 2.8 Ghz laptop), the system comes into a dead stop. Each action I try to do (e.g. moving a window, clicking a button), takes up to 1 minute to happen because nothing is responsive anymore. I would give you some CPU usage statistics if it was for the fact that I can't really launch anything during that time... The hdd goes like crazy, and the most amazing thing is that memory goes to the heavens: from 95 MBs of RAM (on my highly optimized Arch installation with a full Gnome/dbus/hal) to 750 MBs of RAM, from which about 250 MBs are actually swap! This means that when Beagle Indexing kicks in, my laptop's 512 MBs of RAM are *not* enough.

Personally, I am not happy with this situation. I don't think that Novell would release such an app in their OSes if it was to be working like this. I think the bug is in the Arch Linux side. If not, then Beagle must be removed from the public repositories for now until Novell fixes it, or commit a large patch to them that fixes these issues.

I don't even realize that I have Spotlight on my OSX for example, but I feel Beagle really hard. I just had to actually disable Beagle because of this unresponsiveness.