I really don't think this classifies as a valid bug report if I
understand what you are saying correctly..? You complain that round
tripping  Client -> Tracker - > Client -> Zeitgeist -> Client is slow?

I think we can only care about the speed of pure Client <-> Zeitgeist
interactions. Can you post a simple Python script that illustrates the
problems in a purely ZG related scope? Or at the very least you need to
profile each of these interactions so we can have an idea where the
"bug" is...

slow querying
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Zeitgeist Framework: Confirmed

Bug description:
My DB has exactly 416 subjects

*** events: 416      time:  0.541239023209
*** events: 1      time:  0.0319149494171               # querying mostused 
events where subject.uri is a specific uri
*** events: 2      time:  0.499359130859                 # querying mostused 
events where subject.uri is one of 2 specific uris
*** events: 30      time:  10.8581418991                 # querying mostused 
events where subject.uri is one of 30 specific uris

I duplicated the queries again...

*** events: 416      time:  0.487861871719
*** events: 1      time:  0.0361568927765
*** events: 2      time:  0.499109983444
*** events: 30      time:  16.0003550053

What is happening in the background is that i query tracker for a string i get 
all matching uris and then query Zeitgeist

you can test with lp:~seif/sezen/sezen2/
You will need ZG trunk to test it

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