SLIDE 1
4.7.2010 | Tampere, Finland | Akademy 2010
4.7.2010 www.kde.org 2
Do we know our resource demands?
- Akonadi?
- Nepomuk?
- Plasma clock?
- KWin compositing?
- 4.4 to 4.5 change?
- …
KDE performance (again) Lubo Luk 4.7.2010 | Tampere, Finland | - - PowerPoint PPT Presentation
KDE performance (again) Lubo Luk 4.7.2010 | Tampere, Finland | - - PowerPoint PPT Presentation
KDE performance (again) Lubo Luk 4.7.2010 | Tampere, Finland | Akademy 2010 Do we know our resource demands? Akonadi? Nepomuk? Plasma clock? KWin compositing? 4.4 to 4.5 change? 4.7.2010 www.kde.org 2 Do we
SLIDE 2
SLIDE 3
4.7.2010 www.kde.org 3
Do we know our resource demands?
- Akonadi?
- Nepomuk?
- Plasma clock?
- KWin compositing?
- 4.4 to 4.5 change?
- …
- Do we care?
SLIDE 4
4.7.2010 www.kde.org 4
Rule of the big three
- “Choose two, you can't have the third”
- For performance: good, efficient, in time
- => performance is always last, unless it's bad
enough to affect “good”
SLIDE 5
4.7.2010 www.kde.org 5
Benchmarking basics
- Use a proper tool
- Really measure what is intended to be
measured
- Minimize noise
- Comparable conditions
SLIDE 6
4.7.2010 www.kde.org 6
System memory
- Forget classic tools like 'top' or 'free'
- KSysGuard
- Exmap
- xrestop
- Processes can be quite expensive
SLIDE 7
4.7.2010 www.kde.org 7
Application memory
- KSysGuard
- Massif
- kdesdk/kmtrace
SLIDE 8
4.7.2010 www.kde.org 8
CPU usage
- QTime
- Callgrind/KCachegrind
- Sysprof
SLIDE 9
4.7.2010 www.kde.org 9
I/O
- strace (-e file)
- SSD
SLIDE 10
4.7.2010 www.kde.org 10
Performance testsuite
- It would be useful to have a set of “standard”
interesting measurements
- Everybody would be able to repeat
- Releases could be compared
- Regressions could be found
- Login time, memory after login, KFoo memory