Bug #42649 THR_LOCK_charset global mutex abused by InnoDB
Submitted: 6 Feb 2009 14:18 Modified: 15 Aug 2009 1:37
Reporter: Domas Mituzas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Charsets Severity:S5 (Performance)
Version:5.0,5.1 OS:Any
Assigned to: Alexander Barkov CPU Architecture:Any

File: Maximum allowed size is 3MB.
Description:
Privacy:

If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-42649.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

[7 Feb 2009 0:27] Miguel Solorzano
Hit count of get_charset and THR_LOCK_charset

Attachment: hit_count_on_vista_64x.png (image/png, text), 204.58 KiB.

[10 Feb 2009 0:15] Marc ALFF
Analysis using the performance schema

Attachment: Analysis-with-performance-schema.txt (text/plain), 16.33 KiB.