[Bug 282704] KDE 4.7 is very slow on ext3 root partition

[Zane Tu]

https://bugs.kde.org/show_bug.cgi?id=282704

--- Comment #32 from Zane Tu <zanetu at gmail.com> ---
(In reply to comment #31)
> (In reply to comment #30)
> knotify4 is doing a lot of reads, probably searching for sounds to reproduce.
> in systemsettings, disable the sound in the notifications, test and, please,
> tell if this makes any  difference in speed.
> If it does, then knotify4 needs a cache for sound files to reproduce.
> If not, we will continue searching for the I/O bottleneck.
> 
> Also, do not forget to take a look at:
> http://userbase.kde.org/Tutorials

# echo 1 > /proc/sys/vm/block_dump
# dmesg | awk '/READ/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c | sort
-rn | head
    462 firefox-bin
    268 Chrome_FileThre
    202 dolphin
    171 chrome
     79 Chrome_DBThread
     45 Chrome_SafeBrow
      1 block
# dmesg | awk '/WRITE/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c |
sort -rn | head
    298 kjournald
     89 Chrome_FileThre
      3 konsole
      2 rs:main
      1 dmesg
# dmesg | awk '/dirtied/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c |
sort -rn | head
    287 chrome-sandbox
      9 Chrome_FileThre
      2 exe
      2 Chrome_SafeBrow
      2 Chrome_HistoryT
      2 Chrome_DBThread
# dmesg | awk '/WRITE|READ|dirtied/ {sub(/\(.*\):/,"",$3); print $3}' | sort |
uniq -c | sort -rn | head
    317 kjournald
    309 Chrome_FileThre
    253 chrome
    187 Chrome_HistoryT
    148 firefox-bin
    125 Chrome_DBThread
    121 dolphin
    105 chrome-sandbox
    103 flush-8:0
      4 rs:main
# echo 0 > /proc/sys/vm/block_dump

The above output were obtained after I selected "No audio output" in "Player
Settings" of "Manage Notifications". There wasn't noticeable change in terms of
startup speed. After thinking for a while, however, I suppose that kde might
not be the only one to blame. The reason is that I have also upgraded chrome
and firefox after upgrading to kde 4.8. It is entirely possible that the
upgraded versions of chrome and firefox require much more I/O than previous
versions. After I chose not to restore chrome and firefox but remaining
processes such as dolphin, konsole and kate at startup, the period between the
time kde was launched and the time harddisk light went off was around 80
seconds, which is acceptable.

-- 
You are receiving this mail because:
You are the assignee for the bug.