After some very thorough analysis, I've concluded that zeitgeist is not
at blame here.

If my understanding of the kernel slab allocator is correct, free()
doesn't actually free the memory from a program's space until the kernel
decides it needs reclaimed. As such, zeitgeist-daemon is not at fault
and probably not actually using all that memory.

** Attachment added: "zeitgeist research.ods"
   
https://bugs.launchpad.net/zeitgeist/+bug/624310/+attachment/2916666/+files/zeitgeist%20research.ods

-- 
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:
  Invalid
Status in Zeitgeist Extensions:
  Invalid
Status in “zeitgeist” package in Ubuntu:
  Invalid

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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/624310/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to