1. 6
  1.  

  2. 1

    The most interesting paragraph, at least to me:

    A side effect of using transaction pooling is that you cannot use prepared statements, as the PREPARE and EXECUTE commands may end up running in different connections; producing errors as a result. Fortunately we did not measure any increase in response timings when disabling prepared statements, but we did measure a reduction of roughly 20 GB in memory usage on our database servers.