5 ms·
> This report describe pgagroal in relationship to 3 other PostgreSQL connection pool implementations, which we will call "a", "b" and "c". Why? Just why! Plea
by maxpert 5y ago
> This report describe pgagroal in relationship to 3 other PostgreSQL connection pool implementations, which we will call "a", "b" and "c".
Why? Just why! Please put up names rather than saving faces for other poolers!
- iruoy 5y agoAlso make the benchmark code open source, so that we can run it on our own hardware and judge it's relevancy.
- hagbarddenstore 5y agoUh... https://www.postgresql.org/docs/current/pgbench.html https://www.postgresql.org/docs/current/pgbench.html ? That's what's being used...
- bigbillheck 5y ago> Why? Just why! Please put up names rather than saving faces for other poolers! It's Larry Ellison's fault: https://en.wikipedia.org/wiki/David_DeWitt https://en.wikipedia.org/wiki/David_DeWitt
- oliwarner 5y agoThis is an [interesting] joke, right?
- bigbillheck 5y agoNo? Oracle started putting clauses in their sales contracts limiting publishing benchmarks because they performed poorly in a published report.
- oliwarner 5y agoI mean in this context. Seems implausible you could sneak a DeWitt Clause into a FOSS license.