Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/sql/docs/mysql/managed-connection-pooling below:

Managed Connection Pooling overview | Cloud SQL for MySQL

Stay organized with collections Save and categorize content based on your preferences.

Preview — Managed Connection Pooling

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. You can process personal data for this feature as outlined in the Cloud Data Processing Addendum, subject to the obligations and restrictions described in the agreement under which you access Google Cloud. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

This page describes what Managed Connection Pooling is and how to use it with your Cloud SQL instances.

Managed Connection Pooling lets you scale your workloads by optimizing resource utilization and connection latency for your Cloud SQL for MySQL instances using pooling. Managed Connection Pooling creates a pool of threads to handle incoming requests. This delivers significant performance improvements, especially for scaled connections, by absorbing sudden connection spikes without overloading the server with a growth in the number of threads.

While you can use Managed Connection Pooling for any transactional workloads, Managed Connection Pooling provides the most throughput and latency benefit with applications that contain short-lived connections, or applications that result in a connection surge.

For long-lived connections, the connection performance using Managed Connection Pooling can be slightly lower than when using a direct connection. In this case, Managed Connection Pooling provides connection scaling when the number of connections is very high. However, for applications that typically establish long-lived connections, you might use direct connections to your instance instead.

For more information on how to enable Managed Connection Pooling, see Configure Managed Connection Pooling.

To use Managed Connection Pooling, your instance must meet the following requirements:

• Your instance must be a Cloud SQL Enterprise Plus edition instance.
• Managed Connection Pooling requires a minimum maintenance version number of MYSQL_$version.R20250304.00_01. For more information, see Perform self-service maintenance.

When you enable Managed Connection Pooling, the ports used by Cloud SQL instances to serve database traffic change. Managed Connection Pooling changes how MySQL handles connections, but the port numbers remain the same. The ports used by Managed Connection Pooling are as follows:

• TCP port 3306: used for direct connections by the MySQL database server. This is the default port number used when directly connecting using mysql client.
• TCP port 3307: used for the Cloud SQL Auth Proxy only connections by the Managed Connection Pooling server. When you use Cloud SQL Auth Proxy to connect to Managed Connection Pooling server, this port number is configured with the Cloud SQL Auth Proxy client and can't be changed.

You can

by using the following configuration parameters:

• max_pool_size: the amount of concurrency for MCP. The default value is number of cores in your database.

Consider the following limitations when using Managed Connection Pooling with your Cloud SQL Enterprise Plus edition instances:

• Enabling Managed Connection Pooling on an existing instance results in a database restart.
• When you use the Cloud SQL API to enable, disable, or configure Managed Connection Pooling, the instance.update API can't contain any other instance configuration updates.

• Create an instance
• Configure Managed Connection Pooling

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4