[performance] Mir is spending at least 8% of its time in __android_log_print()
Bug #1343074 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Daniel van Vugt | ||
0.5 |
Won't Fix
|
Medium
|
Daniel van Vugt | ||
mir (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Mir is spending around 8% of its time in __android_
Related branches
lp:~vanvugt/mir/fastlog
- PS Jenkins bot (community): Approve (continuous-integration)
- Daniel d'Andrada (community): Approve
- Kevin DuBois (community): Approve
- Alan Griffiths: Approve
-
Diff: 113 lines (+48/-8)5 files modified3rd_party/android-deps/std/Log.h (+4/-0)
3rd_party/android-input/android/frameworks/base/services/input/MirLog.cpp (+11/-8)
CMakeLists.txt (+4/-0)
tests/acceptance-tests/CMakeLists.txt (+1/-0)
tests/acceptance-tests/test_macros.cpp (+28/-0)
lp:~vanvugt/mir/fix-1343074-0.5
Rejected
for merging
into
lp:mir/0.5
- Cemil Azizoglu (community): Needs Resubmitting
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Andreas Pokorny (community): Approve
- Kevin DuBois (community): Approve
-
Diff: 113 lines (+48/-8)5 files modified3rd_party/android-deps/std/Log.h (+4/-0)
3rd_party/android-input/android/frameworks/base/services/input/MirLog.cpp (+11/-8)
CMakeLists.txt (+4/-0)
tests/acceptance-tests/CMakeLists.txt (+1/-0)
tests/acceptance-tests/test_macros.cpp (+28/-0)
description: | updated |
Changed in mir: | |
assignee: | nobody → Daniel van Vugt (vanvugt) |
milestone: | none → 0.6.0 |
status: | Triaged → In Progress |
description: | updated |
summary: |
- Mir is spending around 8% of its time in __android_log_print() + Mir is spending at least 8% of its time in __android_log_print() |
summary: |
- Mir is spending at least 8% of its time in __android_log_print() + [performance] Mir is spending at least 8% of its time in + __android_log_print() |
tags: | added: rtm14 |
tags: | added: qa-daily-testing |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
That number is from a desktop with a single pointer (mouse). I expect it could be a higher percentage on touch where the input processing overhead is greater, and the graphics drivers are also related to Android.