MySQL performance is a tuning of the Max_allowed_packet

MySQL restricts the size of packets accepted by the server according to the configuration file.

Sometimes large inserts and updates are limited by the Max_allowed_packet parameter, resulting in failure.

View current configuration

Show VARIABLES like '%max_allowed_packet% ';

The results shown are:

+--------------------+---------+

| variable_name | Value |

+--------------------+---------+

| Max_allowed_packet | 1048576 |

+--------------------+---------+

Modify method

1) Method 1

You can edit the my.cnf to modify (under Windows My.ini) and modify it in the [Mysqld] section or in the MySQL server configuration section.

Max_allowed_packet = 20M

If you can't find the MY.CNF, you can pass

MySQL--help | grep my.cnf

To find the my.cnf file. Under Linux the file is under/etc/.

2) Method 2

(very compromise, very tangled approach)

Go to MySQL server

Run in the MySQL command line

Set Global Max_allowed_packet = 2*1024*1024*10

Then shut down this MySQL server link and then enter.

Show VARIABLES like '%max_allowed_packet% ';

See if the next Max_allowed_packet is edited successfully

Experience Summary:

There are no problems with using methods on many machines, but the November 14, 2011 encounter with a machine is not successful anyway.

Using the command line: Set global max_allowed_packet = 16M;

No, but using

Set global max_allowed_packet = 2*1024*1024*10;

It worked

MySQL performance is a tuning of the Max_allowed_packet