[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 282704] KDE 4.7 is very slow on ext3 root partition
From:       Jaime Torres <jtamate () gmail ! com>
Date:       2012-07-06 7:11:08
Message-ID: bug-282704-17878-xKcXp1RSMG () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #29 from Jaime Torres <jtamate@gmail.com> ---
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 ...

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]