Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Fixed removal of entity | Christian Mollekopf | 2017-12-29 |
| | |||
* | Cleanup | Christian Mollekopf | 2017-12-28 |
| | |||
* | Fixed incremental updates in folder queries | Christian Mollekopf | 2017-12-28 |
| | | | | | | | | | Incremental additions of children in the tree were filtered due to the parent filter. This broke when we started to maintain state, thus causing the filter in datastorequery containing the parent filter to be carried over. Given that the incremental querying of children currently doesn't really add much value (we don't have trees that are large/deep enough), perhaps we're better off using a different approach. | ||
* | Check for errors | Christian Mollekopf | 2017-11-23 |
| | |||
* | Storage debugging code | Christian Mollekopf | 2017-11-21 |
| | |||
* | Added timeouts to sinkloadtest | Christian Mollekopf | 2017-11-15 |
| | |||
* | Ensure the flatbuffer file is built before the tests | Christian Mollekopf | 2017-11-14 |
| | |||
* | Fixed use after free | Christian Mollekopf | 2017-11-14 |
| | |||
* | Fixed warnings | Christian Mollekopf | 2017-11-11 |
| | |||
* | Require valgrind when enabling memcheck | Christian Mollekopf | 2017-11-07 |
| | |||
* | Benchmarks in tests are too fragile | Christian Mollekopf | 2017-11-03 |
| | |||
* | sinkloadtest.py | Christian Mollekopf | 2017-11-03 |
| | |||
* | No benchmarking in tests | Christian Mollekopf | 2017-10-20 |
| | |||
* | Ensure the test passes reliably. | Christian Mollekopf | 2017-10-17 |
| | |||
* | Initial query test | Christian Mollekopf | 2017-10-17 |
| | |||
* | Use QUICK_TRY_VERIFY | Christian Mollekopf | 2017-10-17 |
| | |||
* | pipelinebenchmark | Christian Mollekopf | 2017-10-17 |
| | |||
* | storagebenchmark | Christian Mollekopf | 2017-10-17 |
| | |||
* | dummyresourcebenchmark values | Christian Mollekopf | 2017-10-17 |
| | |||
* | Split up dummyresourcewritebenchmark into datasets that we want to | Christian Mollekopf | 2017-10-17 |
| | | | | display. | ||
* | QUICK_TRY_VERIFY for quick polling in benchmarks | Christian Mollekopf | 2017-10-16 |
| | |||
* | Updated the information we collect for dummyresourcewritebenchmark | Christian Mollekopf | 2017-10-16 |
| | |||
* | Don't do too much benchmarking in the tests | Christian Mollekopf | 2017-10-16 |
| | |||
* | Share variance/maxDifference implementation | Christian Mollekopf | 2017-10-16 |
| | |||
* | hawd def for incremental vs nonincremental comparison | Christian Mollekopf | 2017-10-12 |
| | |||
* | Changed how we record and print the mail query benchmark data. | Christian Mollekopf | 2017-10-12 |
| | | | | | | Each column can represent an individual value, which we can use to record related data. Each row thus represents a new run of the benchmark. | ||
* | We are not reliably staying under 500 | Christian Mollekopf | 2017-10-12 |
| | |||
* | Don't use QTRY_* in a benchmark | Christian Mollekopf | 2017-10-11 |
| | | | | It has a backoff timer inside which skews the time measurements. | ||
* | hawd json output module | Christian Mollekopf | 2017-10-10 |
| | |||
* | No need to make this overly complicated. | Christian Mollekopf | 2017-10-10 |
| | |||
* | Ensure we copy all blobs when copying to another resource | Christian Mollekopf | 2017-10-09 |
| | |||
* | Optimized the incremental update case. | Christian Mollekopf | 2017-10-08 |
| | | | | | | | | | | | | This brings the incremental closer to a regular query (about 1.5 times as bad instead of 3.5 times). For a comparison look at MailQueryBenchmark::testIncremental() The optimization is built on the assumption that we i.e. get an update with 100 revisions, and thus the optimization applies to the case where we have multiple revisions within that batch that are part of the same reduction. In such a case we can avoid redoing the reduction lookup over and over. | ||
* | Benchmark cleanup | Christian Mollekopf | 2017-10-08 |
| | |||
* | The variance of a single value is 0 | Christian Mollekopf | 2017-10-08 |
| | |||
* | Fixed dummyresource write benchmark | Christian Mollekopf | 2017-10-06 |
| | |||
* | Get both maildir and imap sync tests to work | Christian Mollekopf | 2017-09-20 |
| | |||
* | We now get a connectionerror | Christian Mollekopf | 2017-09-20 |
| | |||
* | Benchmark incremental queries | Christian Mollekopf | 2017-09-13 |
| | |||
* | Fixed getUids by type filtering. | Christian Mollekopf | 2017-09-07 |
| | | | | | We used to simply return all uids. Requires "sinksh upgrade" | ||
* | Ensure we monitor resources for status changes that have been created | Christian Mollekopf | 2017-09-02 |
| | | | | | | after the query. This fixes status monitoring when creating a new account. | ||
* | Default to NoStatus for resources until we know more. | Christian Mollekopf | 2017-08-25 |
| | | | | | | This allows the aggregation to ignore resources where we don't have any status information yet, so the account doesn't always end up being offline. | ||
* | Implemented thread merging | Christian Mollekopf | 2017-08-18 |
| | | | | | It can happen that thread messages are not delivered in order, which means we will have to merge threads once all messages are available. | ||
* | Ensure marking as unread works as well | Christian Mollekopf | 2017-08-02 |
| | |||
* | Use imported targets instead of qt5_use_modules | Heiko Becker | 2017-07-29 |
| | | | | | | | | | | | | | | | | | | | From Qt's documentation: "This macro is obsolete. Use target_link_libraries with IMPORTED targets instead." It's only recommended with cmake >=2.8.9 & < 2.8.12. Sink already requires cmake 3.0. One advantage of using the imported targets is, that cmake complains if a target isn't found before it's used, like Qt5Concurrent missing from the find_package_call here. Reviewers: #sink, cmollekopf Reviewed By: #sink, cmollekopf Subscribers: #sink Tags: #sink Differential Revision: https://phabricator.kde.org/D6361 | ||
* | Adjusted docs and test. | Christian Mollekopf | 2017-07-27 |
| | |||
* | Fixed test | Christian Mollekopf | 2017-07-06 |
| | |||
* | Keep notifier alive for notifications of new resources. | Christian Mollekopf | 2017-07-05 |
| | | | | Necessary to get notifications for newly created resources. | ||
* | We have no guarantee when the notification arrives | Christian Mollekopf | 2017-07-05 |
| | |||
* | Ensure we can deal with non-null terminated strings. | Christian Mollekopf | 2017-06-27 |
| | |||
* | Use asyncverify where we can | Christian Mollekopf | 2017-06-14 |
| | | | | | Otherwise the test is not aborted because the job doesn't get any error set |