Check if there is actual difference in the performance if the DB connection pool is using the recommended DB driver class

[zloster]

the recommended DB driver class or maybe it will help with the transaction deadlocks?
Ordering of the updates should help with the transaction deadlocks. (https://gist.github.com/isopov/9af3864888b85c6cffc4 and some comments in the TFB issues/PRs).
Also the Resin documentation strongly recommends usage of the JDBC more advanced connection options if available. The Driver class is a last resort.

Also check the setting of the PostgreSQL about the server-side prepared statement threshold.

[zloster]

Also the Resin documentation: http://caucho.com/resin-4.0/admin/database.xtp#JDBC2.0-ConnectionPoolDataSource

[zloster]

52805 vs 56594 RPS for the DB test. Submitting a PR with only changed the datasource.
The prepared statement threshold is not very helpful for the benchmarks because the very small number of different statements is used - after the warm up and the various test cases we should see statement reuse.
PR is 3365.