zeitgeist team mailing list archive

[Siegfried Gevatter <rainct@xxxxxxxxxx>]

Here's an easy way to check this:

[rainct, zeitgeist-trunk]$ ps -u $USERNAME -o comm,rss | grep zeitgeist-dae
zeitgeist-daemo 13948
[rainct, zeitgeist-trunk]$ ./reproducer.py 
96466
[rainct, zeitgeist-trunk]$ ps -u $USERNAME -o comm,rss | grep zeitgeist-dae
zeitgeist-daemo 31032

** Attachment added: "reproducer.py"
   https://bugs.launchpad.net/zeitgeist/+bug/624310/+attachment/2141202/+files/reproducer.py

-- 
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/624310

Title:
  Large requests increase memory usage considerably

Status in Zeitgeist Framework:
  Confirmed
Status in Zeitgeist Extensions:
  New

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?