On 05/01/2014 12:07 PM, Jos Poortvliet wrote:
Luca, ..... Yes, baloo generates quite a bit of I/O, they've added a patch to throttle
On Monday 28 April 2014 05:22:25 Sam M wrote: that now, I believe. It is actually a kernel issue (anything before 3.14 can not deal well with high I/O). This I/O problem shouldn't take long as Search indexes very fast - thousands of files per second.
In case it bumps into files which can't be indexed, it will try to determine what file is un-indexable and then disable indexing for that file for the future. Unfortunately, determining what file is hard to index takes a while - about 30 minutes of full cpu and IO at most, per broken file. This has been decreased for 3.14.1 to about 5 minutes at most and will stop/not happen on battery power.
Yes, Nepomuk never had this issue because it simply as so slow that it wouldn't eat the entire I/O of a system and I guess the devs use newer kernels that deal with it better so they didn't notice.
....yes, it seems exactly what baloo makes on my pc, no big %of cpu, max 12%, but the pc was very slow and sloggy ... glued.., it seems the same behaviour when I copy large files...., so may be it is a kernel issue not a baloo...:-) ...but I'm for a stop indexing button just becouse baloo is experimental.... and if it has a bug and I need my full pc I can disable it fastly..., and file a bug, the reenable to allow baloo to index for the night..:-) :-) :-) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org