[Zeitgeist] [Bug 695297] [NEW] unused helper ZeitgeistRemoteDataSourceRegistryTest._register_data_source_python_api() is broken

2010-12-29 Thread Markus Korn
Public bug reported: I'm talking about def _register_data_source_python_api(self, *args): mainloop = gobject.MainLoop() self.client.register_data_source(*args, reply_handler=lambda: mainloop.quit(),

[Zeitgeist] [Bug 695311] [NEW] DataSourceRegistry is a huge performance bottleneck

2010-12-29 Thread Markus Korn
Public bug reported: I was wondering today why the timings for inserting events when running our testsuite (or my benchmark scripts) are looking much better than the timings in a 'real' daemon instance. Some Data: * inserting 500 events at once in my benchmarks: ~0.09 sec * inserting the

[Zeitgeist] [Bug 695311] Re: DataSourceRegistry is a huge performance bottleneck

2010-12-29 Thread Markus Korn
** Attachment added: test_insert_events.py https://bugs.edge.launchpad.net/bugs/695311/+attachment/1778807/+files/test_insert_events.py -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework.

[Zeitgeist] [Bug 695087] Re: Invalid cache access

2010-12-29 Thread Markus Korn
*** This bug is a duplicate of bug 598666 *** https://bugs.launchpad.net/bugs/598666 @Siegfried, what exactly are you benchmarking here? Eg. how many different (relevant) values are you using? How do the graphs look if you have some hundred different actors and mimetypes and a wide range of

[Zeitgeist] [Bug 695297] Re: unused helper ZeitgeistRemoteDataSourceRegistryTest._register_data_source_python_api() is broken

2010-12-29 Thread Launchpad Bug Tracker
** Branch linked: lp:zeitgeist -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/695297 Title: unused helper

[Zeitgeist] [Bug 695297] Re: unused helper ZeitgeistRemoteDataSourceRegistryTest._register_data_source_python_api() is broken

2010-12-29 Thread Siegfried Gevatter
Yeah, removed that. Thanks for spotting. ** Changed in: zeitgeist Importance: Undecided = Low ** Changed in: zeitgeist Status: New = Fix Released ** Changed in: zeitgeist Milestone: None = 0.7.0 ** Changed in: zeitgeist Assignee: (unassigned) = Siegfried Gevatter (rainct)

[Zeitgeist] [Bug 695363] [NEW] Python API doesn't expose DataSourceRegistry's enabled status

2010-12-29 Thread Siegfried Gevatter
Public bug reported: def set_data_source_enabled_callback(self, enabled_callback): [...] # TODO: Make it possible to access the return value! ** Affects: zeitgeist Importance: Low Status: New ** Changed in: zeitgeist Importance: Undecided = Low ** Changed in:

[Zeitgeist] [Bug 695311] Re: DataSourceRegistry is a huge performance bottleneck

2010-12-29 Thread Siegfried Gevatter
** Changed in: zeitgeist Importance: Undecided = Medium ** Changed in: zeitgeist Status: New = In Progress ** Changed in: zeitgeist Milestone: None = 0.7.0 ** Changed in: zeitgeist Assignee: (unassigned) = Siegfried Gevatter (rainct) -- You received this bug notification

[Zeitgeist] [Merge] lp:~zeitgeist/zeitgeist/bug695311 into lp:zeitgeist

2010-12-29 Thread Siegfried Gevatter
Siegfried Gevatter has proposed merging lp:~zeitgeist/zeitgeist/bug695311 into lp:zeitgeist. Requested reviews: Zeitgeist Framework Team (zeitgeist) Related bugs: #695311 DataSourceRegistry is a huge performance bottleneck https://bugs.launchpad.net/bugs/695311 For more details, see:

[Zeitgeist] [Bug 695311] Re: DataSourceRegistry is a huge performance bottleneck

2010-12-29 Thread Launchpad Bug Tracker
** Branch linked: lp:~zeitgeist/zeitgeist/bug695311 -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/695311 Title: DataSourceRegistry is a huge performance bottleneck Status

[Zeitgeist] [Bug 691690] Re: DataSourceRegistry should have GetDataSourceForId method

2010-12-29 Thread Siegfried Gevatter
(Uhm, I had send out an e-mail about this earlier but it looks like Launchpad lost it:) There's a typo in my first comment, what I meant is b) or c), not a) or b). That is, the solution I'd prefer is a). After that I'd choose b), since a GetDataSourceForId method by itself (without the signals)

Re: [Zeitgeist] [Merge] lp:~zeitgeist/zeitgeist/bug695311 into lp:zeitgeist

2010-12-29 Thread Seif Lotfy
Review: Approve forgot the +1 -- https://code.launchpad.net/~zeitgeist/zeitgeist/bug695311/+merge/44850 Your team Zeitgeist Framework Team is subscribed to branch lp:~zeitgeist/zeitgeist/bug695311. ___ Mailing list: https://launchpad.net/~zeitgeist

[Zeitgeist] [Bug 691690] Re: DataSourceRegistry should have GetDataSourceForId method

2010-12-29 Thread Jeremy Whiting
Oh, I see what you meant. Yeah, b would be helpful I believe from our standpoint. Then the signals would be consistent. -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/691690