summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAge
...
* Use the folder index for syncing mails.Christian Mollekopf2015-12-22
| | | | | | If we iterate over all mails, all mails that are not in the current folder will not be existing in exists(). If we use the index instead to only get to the mails we need we're in a better situation.
* Avoid using QDir::separatorChristian Mollekopf2015-12-22
| | | | | It really doesn't help us in assembling paths since qt deals with forward slashes just fine
* Added the mail date propertyChristian Mollekopf2015-12-22
|
* A benchmark for resource writing memory usageChristian Mollekopf2015-12-22
|
* Expect what we can rely onChristian Mollekopf2015-12-22
|
* Only load the properties we need.Christian Mollekopf2015-12-22
| | | | ...and adjust the test accordingly with what we expect.
* An automated test that keeps memory usage in check.Christian Mollekopf2015-12-22
| | | | And ensures we scale linearly with the number of entities.
* Generalized the sync algorithms and applied them to mail.Christian Mollekopf2015-12-20
| | | | | Not necessarily the smartest algorithms, but at least they work and are generally applicable.
* Fixed clientapitestChristian Mollekopf2015-12-19
|
* Detect modifications and removals on folders in the maildirresourceChristian Mollekopf2015-12-18
|
* Make queries by id workChristian Mollekopf2015-12-17
|
* Fixed maildirresourcetestChristian Mollekopf2015-12-17
|
* This is how we can look at the memory layoutChristian Mollekopf2015-12-17
|
* All mails must have a different identifier.Christian Mollekopf2015-12-16
|
* Get the maildir resource to work.Christian Mollekopf2015-12-16
| | | | | The subfolder implementation is not according to any standard it seems, but at least it works for now.
* A read-only maildir resource.Christian Mollekopf2015-12-15
| | | | Respectively a first prototype thereof.
* Ensure we process the query also if no resource is available.Christian Mollekopf2015-12-13
|
* Load entities from multiple resourcesChristian Mollekopf2015-12-13
|
* Mail by folder query testChristian Mollekopf2015-12-10
|
* Deal with no available resourcesChristian Mollekopf2015-12-10
|
* Added resource disk usageChristian Mollekopf2015-12-10
|
* Use Akonadi2::Store::ChildrenFetchedRoleChristian Mollekopf2015-12-06
|
* Added TypeIndexChristian Mollekopf2015-12-06
| | | | | A central location for all types to specify what properties are indexed, and how to query them.
* Improved resource access cachingChristian Mollekopf2015-12-03
| | | | | | | | * Smarter caching. ResourceAccess instances close after a timeout, if not reused. * Introduced a start command to avoid race condition when sending commands to a resource that is currently shutting down. * We resend pending commands after we lost access to the resource * unexpectedly.
* Use hawd for dummyresourcebenchmarkChristian Mollekopf2015-12-01
|
* HAWD: Ensure the column order is maintainedChristian Mollekopf2015-12-01
| | | | | | | By turning the columns into an array instead of an object, we can print the values in the same order as in the definition file. Previosly the order was random, and even headers and values were somtimes mixed up.
* Resolve remoteIds during syncChristian Mollekopf2015-12-01
| | | | | | | Remote id's need to be resolved while syncing any references. This is done by the synchronizer by consulting the rid to entity id mapping. If the referenced entity doesn't exist yet we create a local id anyways, that we then need to pick up once the actual entity arrives.
* Test modificationsChristian Mollekopf2015-11-30
|
* Use the ChildrenFetchedRoleChristian Mollekopf2015-11-30
|
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-26 17:27:47 +0000