summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAge
* Test model signalsChristian Mollekopf2015-11-30
|
* CleanupChristian Mollekopf2015-11-28
|
* Removed most uses of SyncListResult and brought back theChristian Mollekopf2015-11-28
| | | | dummyresourcetest
* Introduced a QueryRunner objectChristian Mollekopf2015-11-27
| | | | | | | | The QueryRunner object lives for the duration of the query (so just for the initial query for non-live queries, and for the lifetime of the result model for live queries). It's supposed to handle all the threading internally and decouple the lifetime of the facade.
* Use the new model api in the benchmark and split tests up.Christian Mollekopf2015-11-26
| | | | This way it's possible to i.e. repeatedly only run the reading part.
* Optimize findLastChristian Mollekopf2015-11-25
| | | | | This just gave a 700% boost to query performance from ~2k to 14k reads per second...
* Use Query::parentProperty to express tree queriesChristian Mollekopf2015-11-24
| | | | | That way we don't have to hardcode the parent property, and we can use the property to express non-tree queries as well.
* Fixed buildChristian Mollekopf2015-11-21
|
* The parent is always an object, so we might as well make that explicitChristian Mollekopf2015-11-19
|
* Don't use a smart pointer for the result providerChristian Mollekopf2015-11-18
| | | | We're not doing any lifetime management anyways.
* CleanupChristian Mollekopf2015-11-15
|
* Working folder tree queryChristian Mollekopf2015-11-15
|
* Fixed clientapitestChristian Mollekopf2015-11-15
|
* Query test adjustmentsChristian Mollekopf2015-11-14
|
* DummyResourceTest and QueryTest are passingChristian Mollekopf2015-11-13
| | | | sync has been removed from the query code and is now a separate step
* It's starting to workChristian Mollekopf2015-11-13
|
* A result modelChristian Mollekopf2015-11-10
| | | | | The result model drives the data retrieval and provides the interace for consumers
* Fixed warningsChristian Mollekopf2015-11-08
|
* Fixed shutdown and synchronize commandsChristian Mollekopf2015-10-31
|
* Correctly execute modifications and removalsChristian Mollekopf2015-10-28
| | | | ... also if there are intermediate revisions.
* Made pipeline preprocessing synchronous.Christian Mollekopf2015-10-28
| | | | | | | | | | | | | | | | Instead of having the asynchronous preprocessor concept with different pipelines for new/modify/delete we have a single pipeline with synchronous preprocessors that act upon new/modify/delete. This keeps the code simpler due to lack of asynchronity and keeps the new/modify/delete operations together (which at least for the indexing makes a lot of sense). Not supporting asynchronity is ok because the tasks done in preprocessing are not cpu intensive (if they were we had a problem since they are directly involved in the round-trip time), and the main cost comes from i/o, meaning we don't gain much by doing multithreading. Costly tasks (such as full-text indexing) should rather be implemented as post-processing, since that doesn't increase the round-trip time directly, and eventually consistent is typically good enough for that.
* Comments for the benchmarksChristian Mollekopf2015-10-25
|
* Documentation on what tests are supposed to test.Christian Mollekopf2015-10-24
|
* Avoid hardcoding a made-up resource type for config that doesn't belongChristian Mollekopf2015-10-21
| | | | to a resource
* ClientAPI: Don't require an explicit instance identifierChristian Mollekopf2015-10-21
|
* Added a removeFromDisk method to the resourceChristian Mollekopf2015-10-21
|
* Test & fix live query removalsChristian Mollekopf2015-10-20
|
* Moved more entitystorage functionality back to facade.Christian Mollekopf2015-10-15
| | | | | To avoid unnecessary abstraction layers that don't solve a problem, and to allow facades to customize how entities are loaded.
* Moved test implementations to central location.Christian Mollekopf2015-10-13
|
* Cleanup revisions with a delayChristian Mollekopf2015-10-12
|
* Replay removals.Christian Mollekopf2015-10-11
| | | | | Now we just have to avoid removing the revision too early from the resource.
* Create a new revision for removals as well.Christian Mollekopf2015-10-10
| | | | So we can replay the change.
* Modification and removal in resultsChristian Mollekopf2015-10-10
| | | | | Now we just need to ensure that equality is tested using the ApplicationDomainType::identifier
* Always get the latest revision directly from storageChristian Mollekopf2015-10-10
| | | | We can just as well read the latest available revision from storage.
* Change replayChristian Mollekopf2015-10-10
| | | | | So far only includes modifications and additions, removals are not yet stored as separate revisions.
* Revision cleanupChristian Mollekopf2015-09-29
|
* Work with revisions in store + pipelinetestChristian Mollekopf2015-09-24
| | | | Cleanup of revisions, and revision for removed entity is yet missing.
* Storage: substring search and findLatestChristian Mollekopf2015-09-11
|
* Added support for mails to akonadi and the dummyresource.Christian Mollekopf2015-09-08
| | | | Adding new types definitely needs to become easier.
* GenericFacadeBenchmarkChristian Mollekopf2015-09-07
| | | | genericfacadebenchmark
* Cleaned-up genericresourcebenchmarkChristian Mollekopf2015-08-24
|
* Cleaned-up storagebenchmarkChristian Mollekopf2015-08-24
|
* Bigger field with and less history by defaultChristian Mollekopf2015-08-24
|
* HAWD for the genericresourcebenchmarkChristian Mollekopf2015-08-24
|
* HAWD: Ensure the formatter sorts the rows.Christian Mollekopf2015-08-24
|
* HAWD: Fixed with fieldsChristian Mollekopf2015-08-24
|
* Removed convenience APIChristian Mollekopf2015-08-23
|
* Storage cleanupChristian Mollekopf2015-08-23
|
* Store indexes as named databases in the same db.Christian Mollekopf2015-08-23
| | | | | | Because we also keep using the same transactions this finally makes the resource somewhat performant. On my system genericresourcebenchmark now processes ~4200 messages per second instead of ~280.
* Less noise and better error handling.Christian Mollekopf2015-08-23
| | | | | Trying to read from non-existant databases no longer prints error messages.