zeitgeist team mailing list archive

[Siegfried Gevatter <rainct@xxxxxxxxxx>]

Yup, that is because it updates the "last seen" time and writes the
change to disk. I guess it should only write down this information
before Zeitgeist ends (and if it dies and doesn't get to write it, that
isn't a big problem).

-- 
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 in Zeitgeist Framework:
  New

Bug description:
  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 same 500 events at once in a 'real' zeitgeist session: ~0.185 sec

You can reproduce this tests by running the attached script like

ZEITGEIST_DEFAULT_EXTENSIONS="_zeitgeist.engine.extensions.datasource_registry.DataSourceRegistry" PYTHONPATH=. python /tmp/test_insert_events.py

PYTHONPATH=. python /tmp/test_insert_events.py

and compare outputs.

To simulate the scenario of multiple running instances of the same application, uncomment the lines 26+ in the script, you will get even worse results.