interesting, github says works for both olap+oltp but it was for go, does the same apply to rust as well? I want to try it in browser is wasm available somewhere or is there any plan to support it?
[Edit] looks like it is available for browser here https://stoolap.io/playground/
i will be trying it with my product this weekend, excited to see how it goes.
I would like to see the actual test harness. A 100x improvement is do-able (you're trimming features basically) but I would like to see how you tested it
> But notice the pattern: SQLite’s wins are on simple, single-row operations where both databases are already sub-millisecond. Stoolap’s wins are on the analytical and complex queries where the difference is 10x to 100x+.
So for a great many workloads, particularly multi-user, SQLite will be faster overall, as most application workloads will have many simple single/few row lookup operations per single/few row update operations, and an order of magnitude less complex analytical queries.
But this should be much faster for genuine analytical operations, and better suited to them due to support for things like temporal storage and queries.
Basically the age-old distinction between optimising for OLTP or OLAP operations.
8 comments
[ 0.23 ms ] story [ 22.9 ms ] threadNAPI-RS has no serialisation overhead?
I guess I'm a bit confused but don't want to read AI fuzz further
So for a great many workloads, particularly multi-user, SQLite will be faster overall, as most application workloads will have many simple single/few row lookup operations per single/few row update operations, and an order of magnitude less complex analytical queries.
But this should be much faster for genuine analytical operations, and better suited to them due to support for things like temporal storage and queries.
Basically the age-old distinction between optimising for OLTP or OLAP operations.