https://bugs.kde.org/show_bug.cgi?id=515396
--- Comment #3 from [email protected] --- Thanks for the quick reply and the detailed report of your observations and perceptions. It seems like your observations do line up with what I would expect on older, slow hardware. So that's good. All of the things that you mentioned are slow, are things that I recognize as current bottlenecks. Also the memory usage lines up with my expectation: there are a few things that are kept in memory that are not really needed. I'm trying to tackly these right now, so hopefully this will improve in future versions. I can't promise it will be in the next major release, though. Oh yeah, one more thing: I'm not sure that the memory usage reported by top/htop fully represents reality. I know that the linux kernel tries to be very clever with caching things if there is plenty of memory available (which apparently is the case for you). In other words, it tries very hard to speed things up by caching and pre-caching things into memory, even though the app itself does no caching of its own. I'm not an expert in this matter, but I know that you should take that reported memory usage with a grain of salt. But that reminds me that I should try running something like valgrind again. It's been a while since I've done that. -- You are receiving this mail because: You are watching all bug changes.
