Bug #81070
closed
Update extension list in EM causes 100% CPU load for very long time
0%
Description
After clearing all rows from tx_extensionmanager_domain_model_extension, retrieving the extension list causes 100% CPU load for many minutes.
Server: Ubuntu 16.04 LTS
PHP: 7.0.15
MySQL: 5.7.18 (5.7.18-0ubuntu0.16.04.1 for Linux on x86_64version)
TYPO3: 7.6.18
mysql> show full processlist\G
- 1. row *******************
Id: 30
User: root
Host: localhost
db: NULL
Command: Sleep
Time: 928
State:
Info: NULL - 2. row *******************
Id: 35
User: root
Host: localhost
db: NULL
Command: Query
Time: 0
State: starting
Info: show full processlist - 3. row *******************
Id: 42
User: typo3
Host: localhost:45972
db: typo3
Command: Query
Time: 527
State: Sending data
Info: SELECT a.uid AS uid FROM tx_extensionmanager_domain_model_extension a LEFT JOIN tx_extensionmanager_domain_model_extension b ON a.repository = b.repository AND a.extension_key = b.extension_key AND a.integer_version < b.integer_version WHERE a.repository = 1 AND b.extension_key IS NULL ORDER BY a.uid
Perhaps this is related to this MySQL bug:
High CPU usage issue/stuck queries with 5.7.6-m16
https://bugs.mysql.com/bug.php?id=76402
Updated by Jan Kornblum almost 7 years ago
Seems to be solved in: https://review.typo3.org/#/c/52670/
Updated by Mona Muzaffar almost 7 years ago
- Related to Bug #81097: Extension Manager uses a query on a column that is not indexed added
Updated by Mona Muzaffar almost 7 years ago
- Related to deleted (Bug #81097: Extension Manager uses a query on a column that is not indexed)
Updated by Mona Muzaffar almost 7 years ago
- Is duplicate of Bug #81097: Extension Manager uses a query on a column that is not indexed added
Updated by Mona Muzaffar almost 7 years ago
- Status changed from New to Closed
Closing this ticket in favor of #81097.
They both deal with the same issue but #81097 has a patchset attached to it.
Please continue your discussion over there.
If you think that this is the wrong decision or experience this issue again, then please reopen this ticket or open a new ticket and add a relation to this ticket number.