Thanks for implementing the new JDBC persistence, Prashant! It's great to see that JDBC persistence is more stable under concurrent load now.
Would you be able to share any detailed performance test numbers for the new JDBC Persistence implementation? I believe the doc linked in your message compares old EclipseLink with a draft of Mongo persistence. It would be nice to get similar numbers for JDBC vs. Mongo [1] using the latest code. [1] https://github.com/apache/polaris/pull/1189 Thanks, Dmitri. On Tue, May 13, 2025 at 12:49 PM Prashant Singh <prashant.si...@snowflake.com.invalid> wrote: > Dear Polaris Community, > > Over the few weeks, Polaris Persistence under-went major refactor to get > rid of the transactional dependencies and completely adopt CAS semantics > (Compare and Swap), simplifying the schema. > > As a result I am pleased to announce the new JDBC implementation which is > considerably faster, more scalable, simpler in schema and highly > configurable, is now ready and a new default for the persistence layer. > > We ran the concurrency benchmarks > < > https://docs.google.com/document/d/1RLYaAtNUkgNW3Ef7-BWfF_8RkSK7B7oR/edit#bookmark=id.von5ayuoga6 > > > conducted / contributed in April this year, with JDBC persistence and we > see a 100% success rate compared to roughly ~0% success rate with the > previous default eclipse link, with consistent p90's (< 50 ms) on mixed > workloads. > > You can learn more about configuration and tuning in the: Relation JDBC > Section <https://polaris.apache.org/in-dev/unreleased/metastores/>. > > Cheers, > Prashant Singh >
