Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.0.21-galera
-
None
Description
When switching tables from utf8 to utf8mb4, we're seeing fairly severe performance regressions - queries that used to run in microseconds, now taking 20 seconds to run.
We've run some tests with query and index variations, or there's a summary here.
For a direct comparison, see:
utf8: https://travis-ci.org/tollmanz/utf8mb4-query-time/jobs/82864656
utf8mb4: https://travis-ci.org/tollmanz/utf8mb4-query-time/jobs/82864660
Here's the WordPress tracking ticket. Comment #2 notes that reducing the meta_key column length to 191 (to match the length of the prefix index) fixes the performance issue, but the utf8 character set doesn't have the same problem.
The same behaviour occurs in MySQL, as well.
Attachments
Issue Links
- is part of
-
MDEV-32113 utf8mb3_key_col=utf8mb4_value cannot be used for ref access
- Closed
- relates to
-
MDEV-16413 test performance of distinct range queries
- Closed
-
MDEV-19123 Change default charset from latin1 to utf8mb4
- Closed
-
MDEV-32113 utf8mb3_key_col=utf8mb4_value cannot be used for ref access
- Closed