Showing 1-30 of 56 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
60261 | 2011-02-26 0:59 | 2016-11-12 22:57 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2693 days) | S5 | mysql-cluster-gpl-7.1.9a | Any | Any | Are transaction hints needed in these situation? |
66563 | 2012-08-28 5:37 | 2012-08-28 6:55 | MySQL Server: InnoDB Plugin storage engine | Verified (4230 days) | S5 | 5.1,5.6 | Any | Any | reduce the number of redundant calls to btr_cur_optimistic_insert() |
69118 | 2013-05-02 2:28 | 2013-05-02 14:00 | MySQL Server: Command-line Clients | Verified (3983 days) | S5 | 5.6, 5.7 | Any | Any | Wasted work in method get_table_structure() |
68572 | 2013-03-05 10:57 | 2014-02-19 16:19 | MySQL Server: Federated storage engine | Verified (4040 days) | S3 | 5.5.25a, 5.5.31 | Any | Any | FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables |
64340 | 2012-02-15 14:07 | 2013-06-14 15:35 | MySQL Server: InnoDB Plugin storage engine | Verified (3940 days) | S5 | 5.1.52, 5.1.61 | Any | Any | race on no_flush event during buf_flush_free_margin |
75504 | 2015-01-14 12:52 | 2015-01-22 14:51 | MySQL Server: InnoDB storage engine | Verified (3353 days) | S5 | Any | Any | btr_search_guess_on_hash makes found block young twice? | |
71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (3163 days) | S2 | 5.1, 5.5, 5.6.15, 5.7.7 | Any | Any | Optimizer does NOT use range checks in typical self-join for InnoDB tables |
62018 | 2011-07-28 15:15 | 2018-02-11 20:45 | MySQL Server: InnoDB storage engine | Verified (4089 days) | S5 | 5.6.3 | Any | Any | innodb adaptive hash index mutex contention |
75962 | 2015-02-19 3:14 | 2015-03-03 20:46 | MySQL Server: InnoDB storage engine | Verified (3313 days) | S3 | 5.6.24, 5.7.6 | Any | Any | Innodb calls fsync when freeing a LRU page to fulfill page request |
81376 | 2016-05-11 6:48 | 2018-07-16 8:12 | MySQL Server: InnoDB storage engine | Verified (2877 days) | S5 | 5.7 | Any | Any | Single page flushing should be removed |
30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3095 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
81630 | 2016-05-28 5:46 | 2016-08-31 6:30 | MySQL Server: Replication | Verified (2766 days) | S5 | 5.7.12 | Any | Any | MySQL 5.7 is 37-45% slower then 5.6 when using binlogging due to defaults change |
35165 | 2008-03-08 17:48 | 2022-12-04 20:45 | MySQL Server: CSV | Verified (5860 days) | S5 | 5.1 | Any | Any | Logging to table is slow for large queries |
75981 | 2015-02-20 13:56 | 2017-11-05 7:12 | MySQL Server: InnoDB storage engine | Verified (3276 days) | S5 | 5.7.6 | Any | Any | MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write |
74408 | 2014-10-15 19:52 | 2018-07-04 15:16 | MySQL Server: InnoDB storage engine | Verified (2094 days) | S5 | 5.6, 5.7, 8.0 | Any | Any | srv_conc_enter_innodb() is not optimal |
91585 | 2018-07-10 1:16 | 2018-08-27 11:06 | MySQL Server: Stored Routines | Verified (2088 days) | S5 | 5.7, 8.0, 8.0.11, 5.7.23 | Any | Any | “dead” code inside the stored proc or function can significantly slow it down |
98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1490 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
99432 | 2020-05-04 8:09 | 2020-05-05 12:04 | MySQL Server: InnoDB storage engine | Verified (1424 days) | S5 | 8.0.20 | Any | ARM | Improving memory barrier during rseg allocation |
100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1331 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
100119 | 2020-07-06 7:07 | 2020-08-14 13:55 | MySQL Server: InnoDB storage engine | Verified (1322 days) | S5 | 8.0.20 | Any | ARM | Switch to use relaxed memory barrier for redo-log counters |
100091 | 2020-07-02 12:23 | 2020-07-03 8:48 | Connector / Python | Verified (1364 days) | S5 | 8.0.18, 8.0.20 | Any | Any | mysqlx interface is a lot slower than the connector.python interface |
104615 | 2021-08-13 10:26 | 2021-08-13 11:36 | MySQL Server: Logging | Verified (958 days) | S5 | 8.0 | Any (rhel7.4) | Any (intel-x86) | trx commit slow if there are too many binlog files to purge while rotating |
110779 | 2023-04-24 11:32 | 2023-05-12 5:49 | MySQL Server: Optimizer | Verified (321 days) | S5 | 8.0.33, 5.7.42 | Any | Any | IN clause cause pick bad performan index |
114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (35 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4853 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5484 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
40367 | 2008-10-28 8:55 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5544 days) | S3 | 5.1.28, 5.1.29, 5.0, 5.1 bzr | Any | Any | SHOW on a broad view is taking too long |
44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5035 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
50367 | 2010-01-15 14:12 | 2011-02-16 23:44 | MySQL Server: General | Verified (5124 days) | S5 | 5.1.42, 5.1 bzr | Any (MS Windows 32 bits, Mac) | Any | REPLACE has quadradic computational complexity on windows server (but not linux) |
38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5722 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
Showing 1-30 of 56 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |