All my kudos for the OrioleDB team, they have been working for years with the Postgres core devs to get the extensibility patches they need for their storage extensions merged back.<p>It’s not just about building their extension but actually making Postgres better for everyone. I would have loved that big corps would have taken this approach, as it opens the doors to others to add features for different use cases and making postgres more of a DBMS framework
Some notable benchmarks from the OrioleDB beta7 release:<p>* 5.5x Faster at 500 Warehouses: In TPC-C benchmarks with 500 warehouses, OrioleDB outperformed PostgreSQL's default heap tables by 5.5 times. This highlights significant gains in workloads that stress shared memory cache bottlenecks.<p>* 2.7x Faster at 1000 Warehouses: Even when the data doesn't fit into the OS memory cache (at 1000 warehouses), OrioleDB was 2.7 times faster. Its index-organized tables improve data locality, reducing disk I/O and boosting performance.<p>Try it yourself:<p>Clone the OrioleDB repository from GitHub and follow the build instructions, or use their Docker image.
<a href="https://github.com/orioledb/orioledb#installation">https://github.com/orioledb/orioledb#installation</a>
Alternatively, run OrioleDB on Supabase. Read the blog post for more details.
<a href="https://supabase.com/blog/orioledb-launch">https://supabase.com/blog/orioledb-launch</a><p>Run your own workloads or existing benchmarks like go-tpc or HammerDB to see the performance differences firsthand. We Would love to hear about others' experiences with OrioleDB, especially in production-like environments or with different workloads.
> Our roadmap includes support for multi-master configurations, enhancing availability and fault tolerance. This will allow for read and write operations across multiple nodes, improving performance and resilience.<p>Fu--ing finally!
Can people please, for the love of god, stop running tpcc with think time disabled. When run in this way it is not the TPC-C benchmark, and is not "simulating real database workloads that is considered a modern standard in database applications." TPC-C generally has an open-loop traffic arrival rate that scales with the size of the data and is lightly contended. When run without think time, it becomes closed loop, and generally dominated by the contention that was not supposed to be dominant.<p>This instance is less bad than some in that it's at least comparing the same sort of database and doing it using the same driver -- so it is at least an apples to apples measurement of something.<p>Still, please, as a community we need to stop getting rid of the think time and quoting the output as tpmC or as a standard benchmark.<p>See <a href="https://www.tpc.org/tpc_documents_current_versions/pdf/tpc-c_v5.11.0.pdf" rel="nofollow">https://www.tpc.org/tpc_documents_current_versions/pdf/tpc-c...</a> for the spec.