Large requests increase memory usage considerably
Bug #624310 reported by
Michal Hruby
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Extensions |
Invalid
|
Undecided
|
Unassigned | ||
Zeitgeist Framework |
Invalid
|
Low
|
Unassigned | ||
zeitgeist (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
I'm seeing with standalone Sezen that after running it, mem usage of the zeitgeist-daemon process goes up from ~13MB to ~40MB, this is understandable as when Sezen is starting, it does one big query where it asks for everything grouped by most recent subjects and in my case this returns ~11 thousand events, so the extra 30MB can be explained by allocating memory for the DBus reply.
Still, my question is whether Zeitgeist should be at mercy of the applications, where nothing prevents them from spiking the memory usage of the core process. (I already saw a couple of times zeitgeist using 80-100MB of memory on my system). Perhaps there's a way to tell python dbus to free its buffers?
Related branches
Changed in zeitgeist: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 0.5.1 |
Changed in zeitgeist: | |
milestone: | 0.5.1 → 0.6 |
importance: | High → Undecided |
Changed in zeitgeist: | |
milestone: | 0.7.0 → none |
Changed in zeitgeist: | |
milestone: | none → 0.8.0 |
Changed in zeitgeist: | |
milestone: | 0.8.0 → 0.8.1 |
Changed in zeitgeist: | |
importance: | Undecided → Low |
status: | Confirmed → In Progress |
milestone: | 0.8.1 → none |
Changed in zeitgeist (Ubuntu): | |
importance: | Undecided → Low |
To post a comment you must log in.
I'd actually guess that the memory was allocated inside sqlite rather than python-dbus, but that's hard to tell without really profiling it.