[Bug 282704] KDE 4.7 is very slow on ext3 root partition
zanetu at live.com
zanetu at live.com
Fri Jul 6 10:49:45 BST 2012
https://bugs.kde.org/show_bug.cgi?id=282704
--- Comment #30 from zanetu at live.com ---
(In reply to comment #29)
> Can you execute the followings commands as root to see what kind of I/O and
> what processes are causing it?
>
> before you start the slow process (or KDE session)
>
> echo 1 > /proc/sys/vm/block_dump
>
> after it is running
>
> dmesg | awk '/READ/ {sub(/\(.*\):/,"",$2); print $2}' | sort | uniq -c |
> sort -rn | head
> dmesg | awk '/WRITE/ {sub(/\(.*\):/,"",$2); print $2}' | sort | uniq -c |
> sort -rn | head
> dmesg | awk '/dirtied/ {sub(/\(.*\):/,"",$2); print $2}' | sort | uniq -c |
> sort -rn | head
> dmesg | awk '/WRITE|READ|dirtied/ {sub(/\(.*\):/,"",$2); print $2}' | sort |
> uniq -c | sort -rn | head
> echo 0 > /proc/sys/vm/block_dump
>
> to know the processes to blame.
> NOTE: If you not see program names, only numbers, replace $2 with $3.
>
> seen at
> http://balajitheone.blogspot.com.es/2011/04/io-wait-load-tracking-to-process.
> html
>
> The main problem with this bug is that there are no tools to know where are
> the I/O bottlenecks in a program (or I do not know any). (just like
> callgrind but for I/O)
> Therefore, we do not know (yet) if this is for opening/closing a lot of
> files, syncing files, or ...
# echo 1 > /proc/sys/vm/block_dump
# dmesg | awk '/READ/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c | sort
-rn | head
152 chrome
149 knotify4
117 Chrome_FileThre
64 Chrome_DBThread
63 firefox-bin
51 Chrome_CacheThr
36 Chrome_SafeBrow
19 PAC
4 Chrome_IOThread
1 Chrome_ProcessL
# dmesg | awk '/WRITE/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c |
sort -rn | head
210 kjournald
174 flush-8:0
57 firefox-bin
5 konsole
3 rs:main
1 chrome-sandbox
# dmesg | awk '/dirtied/ {sub(/\(.*\):/,"",$3); print $3}' | sort | uniq -c |
sort -rn | head
253 chrome-sandbox
93 knotify4
54 Chrome_FileThre
7 Chrome_CacheThr
5 firefox-bin
1 Chrome_DBThread
# dmesg | awk '/WRITE|READ|dirtied/ {sub(/\(.*\):/,"",$3); print $3}' | sort |
uniq -c | sort -rn | head
1212 kjournald
170 flush-8:0
120 Chrome_SyncThre
112 Chrome_FileThre
33 Chrome_HistoryT
25 Chrome_DBThread
18 chrome
12 firefox-bin
5 Chrome_CacheThr
2 WorkerPool/6761
# echo 0 > /proc/sys/vm/block_dump
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list