Python continues to get better async support and with that comes pressure to switch. See the realistic effects that switching to async would have on your web servers.
It wasn’t clear whether they have a connection proxy in front of the postgres instance. PosrgreSQL connections are expensive, so something like pg_bouncer could also make a big difference here.
(I realize the point was to test python web servers, but it would have been an interesting additional metric.)
No connection proxy in this case. The pooled sync test uses client side pooling which shows better performance. Using a proxy would have the same effect, just moves the pooling to server side.
It wasn’t clear whether they have a connection proxy in front of the postgres instance. PosrgreSQL connections are expensive, so something like pg_bouncer could also make a big difference here.
(I realize the point was to test python web servers, but it would have been an interesting additional metric.)
No connection proxy in this case. The pooled sync test uses client side pooling which shows better performance. Using a proxy would have the same effect, just moves the pooling to server side.