--- schema_version: "1" id: 5483e551906e395e25501d05ccf9c27a48a97b8e3a5fb8bb441eb59eda08af6d title: Pooling Profiles collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/tuning-pooling-profiles.md canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/tuning-pooling-profiles source_site: docs.mulesoft.com content_type: documentation content_hash: 4287c5ecc2f64e974e53ed1d182fab39e336a1b9db3e44f8d3a6e9e04f70b400 description: MuleSoft Documentation Site release: "4.3" latest: false --- --- product: Mule Runtime version: 4.3 --- # Pooling Profiles > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Unlike singleton components, pooled components configure their component pool which contains multiple instances of the component to process simultaneous incoming requests. Each pooled component has its pooling profile. Connectors such as Anypoint Connector for FTP (FTP Connector) and Anypoint Connector for SFTP (SFTP Connector) pool connections by default and use a `pooling-profile` to customize the connection pool. When performance tests show it necessary, add the `pooling-profile` parameter to connectors. However, Anypoint Connector for Database (Database Connector) does not perform connection pooling by default, causing every execution of an SQL statement to open a new connection and close it once finished (unless there is a transaction active that uses the same connection for the whole transaction). By using a pooling profile, you enable one-time connection setup and subsequent requests use existing connections, thereby improving request-processing performance: ```xml ``` The `maxPoolSize` setting specifies the maximum number of connections open to the database, and available to serve incoming requests.