| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Made pipeline preprocessing synchronous. | Christian Mollekopf | 2015-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 benchmarks | Christian Mollekopf | 2015-10-25 |
| | | |||
| * | Moved test implementations to central location. | Christian Mollekopf | 2015-10-13 |
| | | |||
| * | Cleaned-up genericresourcebenchmark | Christian Mollekopf | 2015-08-24 |
| | | |||
| * | HAWD for the genericresourcebenchmark | Christian Mollekopf | 2015-08-24 |
| | | |||
| * | Store indexes as named databases in the same db. | Christian Mollekopf | 2015-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. | ||
| * | GenericResourceBenchmark | Christian Mollekopf | 2015-08-19 |
| Will eventually replace most parts of DummyResourceBenchmark | |||
 |
index : sink | |
| A data access layer handling synchronization, caching and indexing |
| summaryrefslogtreecommitdiffstats |