Auto managed connection pooling for MySQL add-ons

Starting today, we provide ProxySQL, a MySQL proxy, on all of our managed instances for out of the box connection pooling to your MySQL add-ons.

ProxySQL acts as a local proxy between your application and your MySQL add-on. Your application will be able to connect to ProxySQL which will then forward your requests to the linked MySQL add-on.

A connection pool will cache your database connections and keep them open for future requests

Thanks to the connection pool, your database connections will be cached and your application won’t have to wait for the connection to be established to your add-on. This can lead to faster response time when a lot of requests are executed. It also solves the problem of too many opened connections to the database. You will be able to do as many queries as you need without getting a “user max connection exceeded” error. ProxySQL will queue all the requests until a connection slot is available.

Sidenote: ProxySQL is not available on Docker instances as we do not manage your Dockerfile.

Configure ProxySQL

To enable ProxySQL for your application, you first need to have a MySQL add-on linked to your application. You then have to set the CC_ENABLE_MYSQL_PROXYSQL=true environment variable.

Once enabled, the CC_MYSQL_PROXYSQL_SOCKET_PATH environment variable will be injected during the deployment phase. It provides a Unix Domain Socket path to use to connect to ProxySQL.

There are also two other environment variables you can set to configure ProxySQL to match your needs:

  • CC_MYSQL_PROXYSQL_USE_TLS: A boolean (true or false) to enable TLS between ProxySQL and your MySQL add-on. Defaults to true.
  • CC_MYSQL_PROXYSQL_MAX_CONNECTIONS: An integer which defines how many maximum connections ProxySQL will open to your MySQL add-on. Defaults to 10. You can refer to our ProxySQL documentation to learn more about how you should compute the maximum connection value when auto scalability is involved.


Here are some examples on how to connect to ProxySQL using various languages:

PHP using PDO

Using PDO, you have to use the unix_socket option in your DSN:

// This variable is injected during the deployment
$socket = getenv("CC_MYSQL_PROXYSQL_SOCKET_PATH");
// Get the database name from the environment
$db = getenv("MYSQL_ADDON_DB");
// Get the database user from the environment
$user = getenv("MYSQL_ADDON_USER");
// Get the database password from the environment
$pass = getenv("MYSQL_ADDON_PASSWORD");
$dsn = "mysql:unix_socket=$socket;dbname=$db";
try {
  $pdo = new PDO($dsn, $user, $pass);
} catch (PDOException $e) {
  throw new PDOException($e->getMessage(), (int)$e->getCode());


For WordPress, you can change the DB_HOST variable in your wp-config.php:

// To connect using a unix socket, the syntax is: `localhost:/path/to/socket`
define('DB_HOST', "localhost:" . getenv("CC_MYSQL_PROXYSQL_SOCKET_PATH") );
// Get the database user from the environment
define('DB_USER', getenv("MYSQL_ADDON_USER"));
// Get the database password from the environment
// Get the database name from the environment
define('DB_NAME', getenv("MYSQL_ADDON_DB"));


On Node.js, using the mysql npm package, you have to set the socketPath property :

const mysql      = require('mysql');
const connection = mysql.createConnection({
  // Get ProxySQL unix domain socket path from the environment
  socketPath : process.env["CC_MYSQL_PROXYSQL_SOCKET_PATH"],
  // Get the database user from the environment
  user       : process.env["MYSQL_ADDON_USER"],
  // Get the database password from the environment
  password   : process.env["MYSQL_ADDON_PASSWORD"],
  // Get the database name from the environment
  database   : process.env["MYSQL_ADDON_DB"]
connection.connect(function(err) {
  if (err) {
    console.error('error connecting: ' + err.stack);

  console.log('connected as id ' + connection.threadId);


ProxySQL exposes some metrics using the Prometheus format. Those metrics are automatically collected into our Metrics system and can be accessed in the Advanced Metrics view of your application. This allows you to track how effective your connection pool is and how many request your instances are making. You can get the list of metrics we expose in our ProxySQL documentation


You can find more information about this feature in our ProxySQL documentation.


Using ProxySQL may help decrease the response time of your application if it does a lot of SQL requests. We’d love to hear from you on how ProxySQL’s connection pool affected your applications performances.


À lire également

Deploy llama, mistral, openchat or your own model on Clever Cloud

If AI has been in the news recently, it's mainly through large language models (LLMs), which require substantial computing power for training or inference. Thus, it's common to see developers using them via turnkey APIs, as we did in a previous article. But this is changing thanks to more open and efficient models and tools, which you can easily deploy on Clever Cloud.

Our consortium, InfrateX, wins Simpl

The InfrateX Consortium, led by Sopra Steria with NTT Data and including Clever Cloud as a member, has won the significant contract Simpl.
Company Press

Our end-of-year events

The end of the year is already shaping up to be full of events, trade…