** Changed in: zeitgeist (Ubuntu)
Importance: Undecided = Low
--
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
** Also affects: zeitgeist (Ubuntu)
Importance: Undecided
Status: New
--
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
** Changed in: zeitgeist
Importance: Undecided = Low
** Changed in: zeitgeist
Status: Confirmed = In Progress
** Changed in: zeitgeist
Milestone: 0.8.1 = None
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for
So i created a shitty extension too see how much memory consumption happens
before things are sent over dbus.
The idea is I ask for ALL events directly from the engine, 10 seconds after
zeitgeist starts
Here are my observations
find_eventids: starts with 16.8 MB and end up with 25.4 MB
and here is the vala test ?field.comment=and here is the vala test
** Attachment added: test.vala
https://bugs.launchpad.net/zeitgeist/+bug/624310/+attachment/2153966/+files/test.vala
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the
for the last 2 scripts make sure you change the path to the DB
--
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
** Changed in: zeitgeist
Milestone: 0.8.0 = 0.8.1
--
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
Before we freak about about __slots__ and structs I think we need hard
evidence that we lose all this memory to Events and Subjects. Attaching
some profiler to the Python VM should sort this out quickly. And why
doesn't Ubuntu show the same symptoms?
--
You received this bug notification because
I had a brief discussion with the guys on #python
---
seiflotfy can u explain to me why inheriting from object with __slots__ uses
less memory than inheriting from list? make it for dummies so i can explain it
to my team
verte seiflotfy: do you know what a struct looks like in memory?
Based on what I posted above I noticed that in our datamodel.py Event
and Subject both inherit from list which could cause the excessive
memory usage. I think we should look into re-implementing them as
objects with all the necessary additions like __getitem__ and
__setitem__ to avoid breaking
So using fedora 32-bit Zeitgeist consumes about 90 MB after a few hours
I am using Synapse and GNOME Shell.
--
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:
Is there a posibility this bug is related with this one in Unity?:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/757727
If so, is it being worked on?
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist
** Changed in: zeitgeist
Milestone: 0.7.0 = None
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
Ok I don't think this issue will be tackled for 0.6 now so postponing
for 0.7
** Changed in: zeitgeist
Milestone: 0.6 = 0.7
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
I've made some tests tonight, on an activitylog with 18k random web history
events.
The in memory size of the daemon is about 7MiB on startup.
After running
FindEvents(TimeRange.until_now(), [],StorageState.Any, 0,1)
(same query is used by sezen *over and over again*)
the daemon's memory
As far as I remember, the main reason why we dropped this iterator thing being
part of our API redisign efforts a year ago was that there is no easy (and
performant) way to do batched database queries. The problem is: we don't have a
'stable' order of events, just think of a query which returns
OK now it all makes sense again. Sorry guys.
On another note I found a nifty tool for memory profiling.
http://guppy-pe.sourceforge.net/
Let's see what we can do with that
http://guppy-pe.sourceforge.net/Cheers
Seif
On Sat, Oct 2, 2010 at 11:13 AM, Markus Korn thek...@gmx.de wrote:
As far as I
Seif, that's what we have FindEventIds for.
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
I know yet the iteration is handeled then from the client side... I am
suggesting a way to do it completely from the engine side :)
On Fri, Oct 1, 2010 at 10:00 PM, Siegfried Gevatter
rai...@ubuntu.comwrote:
Seif, that's what we have FindEventIds for.
--
Large requests increase memory usage
** Changed in: zeitgeist
Milestone: 0.5.1 = 0.6
** Changed in: zeitgeist
Importance: High = Undecided
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of Zeitgeist
Framework Team, which
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.
--
Large requests increase memory usage considerably
https://bugs.launchpad.net/bugs/624310
You received this bug notification because you are a member of
Come to think of it - the fact that Sezen requests 11k events also
suggests that there is something wrong in the design scope of either
Zeitgeist or Sezen.
Before we loose our selves on an optimization cache-pruning spree (which
may very well consume a lot of development time for some very small
22 matches
Mail list logo
