I've looked at some other framework tests which use postgresql, they don't set their connection pools to 256 (See links below).
I'm not sure what the optimal pool size should be, but assuming that there is one isolate per core, and one pool per isolate, then 2-3 connections per isolate is probably the ideal level.
The problem with using a large number of connections is that Postgresql doesn't virtualise connections at all. So for each connection the server starts a new backend process. It is up to the application to pool connections, or to use an external connection pool like pgbouncer. By default postgresql is configured to only allow a maximum of 100 connections. However for techempower somebody has foolishly increased this to 1000 to get their benchmark to work correctly - they should have used a pool instead. This setting will reduce postgresql performance as well. If I ever find time, I'll see if I can talk them into fixing this. But at the moment, I'd rather spend my limited time on improving the dart postgresql driver, there are some very low hanging fruit that should be able to give it a good bump in performance.
Another point is that there aren't very many postgresql benchmarks in techempower - so it would be nice to see a dart-mysql benchmark for better apples to apples comparisons.
I've opened a bug here - if any one feels like porting the benchmark - perhaps reply to this ticket so James can review it, and send you patch to techempower.
Here's some links to the techempower postgresql configs:
The test called servlet-postgresql-raw appears to be using the resin default of 5 database connections.
https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/frameworks/Java/servlet/src/main/webapp/WEB-INF/resin-web.xml
Undertow uses a default too. Not sure what it is.
Aspnet also uses a default. Not sure what it is.