Skip to main content
All CollectionsDomains, Web Servers, and BeyondDatabases
What are the recommended Max allowed packet size & Max connections number for database? (avoid extreme loading time for AJAX; ex. activity feed)
What are the recommended Max allowed packet size & Max connections number for database? (avoid extreme loading time for AJAX; ex. activity feed)
Rapyd Team avatar
Written by Rapyd Team
Updated over a week ago

For any web application, particularly those reliant on AJAX calls such as activity feeds, the database's performance is paramount. The database's efficiency can often hinge on specific configuration settings, primarily the Max allowed packet size and Max connections. This article will delve into recommendations for these settings to maintain swift AJAX responses and optimal database interactions.

Efficient database operations are at the heart of responsive web applications. By optimizing settings like the Max allowed packet size and Max connections, we can sidestep potential performance pitfalls. Here we'll dissect these configurations, emphasizing their impact on AJAX operations and suggesting optimal values.

Understanding Max allowed packet size

This parameter defines the maximum amount of data that can be sent in a single packet over a network. The packet size is not only vital for database operations but also for smooth AJAX interactions. A too-small value may truncate data or cause failed transactions, while an excessively large value could lead to memory wastage.

Benefits of Optimizing Packet Size

  1. Smooth Data Transfers: Suitable packet sizes ensure data, especially large chunks, are transmitted efficiently.

  2. Error Minimization: Helps avoid 'Packet too large' errors.

  3. Enhanced Performance: Optimized sizes prevent the overhead of breaking data into many small packets.

For web applications with heavy AJAX interactions, it's recommended to set the Max allowed packet size to at least 16M to 64M, depending on the specific use-case and the size of data transactions.

Unraveling the Max connections Setting

This setting determines the maximum number of concurrent connections a database can handle. Connections include those from web servers, application servers, and other client applications.

Implications of Connection Limits

  1. Performance: If connections exceed the limit, new ones will be queued or rejected, affecting site performance.

  2. Resource Allocation: More connections mean more memory consumption. It's essential to balance based on available server resources.

  3. Concurrency: High traffic sites with many simultaneous users need a higher connection limit.

A general recommendation is to start with a Max connections setting of 150 to 200 for medium-sized applications. However, this should be adjusted based on server resources and traffic patterns.

Striking the Right Balance

Optimizing database settings is an act of balance. While you want to allocate sufficient resources for smooth operations, it's equally crucial not to waste or overcommit resources. Regularly monitor and adjust based on observed performance and evolving requirements.


Maintaining rapid AJAX responses and efficient database interactions is often a matter of correctly configuring the database. By understanding and optimizing the Max allowed packet size and Max connections, administrators can bolster both database and overall application performance. Regular evaluations and adjustments to these settings, based on real-world use and feedback, are the keys to sustained efficiency.

Did this answer your question?