On Mon, 2008-01-14 at 12:35 +0100, Clayton wrote:
I see a few people here saying Beagle runs fine for them with no noticeable impact on performance... how?
It seems that you monitor Beagle in a first time after installation. Though there is pops up note telling that computer will be slower in a first few minutes. Later on you shouldn't notice indexing.
I let Beagle run longer than 24h on the dual core system. System response remained horrible. A friend installed 10.2 and then updated everything including Beagle... it ran for a couple of weeks with Beagle killing his system performance before he called and asked what was wrong. So, I am not talking 30 seconds of annoyance here... this is days of uptime on fast machines... and weeks on slower machines.
version is 'beagle-0.2.18-30' which by any interparetation of version string is early development. On the other hand, how many people will ever attempt to test software with so low version (except Linux users)?
Test by choice is a good thing... lots of us here install from Factory just to see what works. I have a VM I do that in all the time. Lots of things break and I have to roll back to a previous snapshot (which is why I like to use a VM instead of a native system)
Setting it as part of the default install makes the new users test it as well. That isn't giving the new user a lot of choice.
with basically no data, but about 1.2TB of data on other mount points.
Which you could tell beagle not to index. That's a lot of data.
True, but a significant portion of it is video. Mostly very large files eating up a lot of that diskspace.... not millions of small text files that need to be indexed. Indexing 2 or 3 hundred binary video files should not take that long.
C.
Since noone seems to have brought this up before... http://beagle-project.org/Troubleshooting_CPU -- Kevin "Yo" Dupuy | Public Email: <kevin@kevinsword.com> Happy New Year from Yo.media! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org