https://bugs.kde.org/show_bug.cgi?id=400704
--- Comment #26 from rich...@meinsen.net --- Hi the comming change from actual to file size is good, also the change from expected to used. the link concerning 120% is not really clear to me. some sum was changed. but the ouput still remains unexplained, 120% of what. i understand that you identified the database layout as *the* problem. from my point of view i'd see the cpu (-> io) greed as an problem. in another thread there was the statment that it works better/less blocking the system with other schedulers. it really would be ok, at least for me, if the indexing is done silently in background and not as fast as posslble, blocking the system. looks independent from db schema changes to me. at the moment I work with ml datasets -> archive files, but below GB size. it looks as if the baloo_file_extr ist the process to be blamed. currently: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND **** user 39 19 259,7g 13,6g 10,3g R 97,0 70,5 355:49.30 baloo_file_extr I let it run the whole night to get through his work - not ready yet. still freezing the system (even mouse) quite often. as written i'd be ok to not index these files as fast as possible. and i can't really understand how it can take 7 hours of fast cpu time to index less than sub gb archives for the baloo_file_extr. looks independent from db schema changes to me. you didn't answer the point that one can see what baloo is currently doing. that could help a) for debugging and b) adjusting/excluding directories/files from indexing. with options to tune indexing like - don't index when (allow combinations) -- filetype -- if size is smaller/bigger -- is is more/less than timespan at specific disk location -- is is more/less than timespan created / modified and a monitor command that allows to see the freeze causes in realtime and a log that allows to see the freeze causes (files) later (log start indexing / stop index of file) (when indexing it takes more than ___ minutes between start and stop, when indexing took more than ___ minutes since start it, .... . this looks independent from db schema changes to me and being able to tune baloo just to not do some things it has problems with would help to optimize the usability until the big rewrite is done. it's a question how priorities are set. -- You are receiving this mail because: You are watching all bug changes.
