Bug 270863 - Create benchmark tests to check Nepomuk performance
Summary: Create benchmark tests to check Nepomuk performance
Status: RESOLVED NOT A BUG
Alias: None
Product: telepathy
Classification: Unmaintained
Component: nepomuk-service (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR task
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-13 19:32 UTC by George Goldberg
Modified: 2013-06-12 20:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Goldberg 2011-04-13 19:32:47 UTC
Create some test cases that push Nepomuk to the limits of what we are likely to need (I'm thinking 1,000 contacts with presence changes being received for 2 or 3 contacts a second). These tests should be easy to run (as unit tests) and record meaningful quantitative data as to the performance. They should probably be run directly on the NepomukStorage class with the methods being invoked directly by the test case, since it is only Nepomuk performance we are trying to assess.
Comment 1 David Edmundson 2013-06-12 20:39:07 UTC
Presence changes no longer go through nepomuk
(plus this has been open for 2 years with no work, it won't happen any time soon)

Loading  is benchmarked inside libkpeople.