Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lesuisse/repro-issue-percona-high-cpu-usage-select-for-update
https://github.com/lesuisse/repro-issue-percona-high-cpu-usage-select-for-update
Last synced: 16 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/lesuisse/repro-issue-percona-high-cpu-usage-select-for-update
- Owner: LeSuisse
- License: mit
- Created: 2024-06-05T12:05:00.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2024-06-05T12:49:57.000Z (5 months ago)
- Last Synced: 2024-10-08T13:19:13.503Z (about 1 month ago)
- Language: PHP
- Homepage: https://perconadev.atlassian.net/browse/PS-8839
- Size: 45.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Quick (& dirty) reproduction scenario of high CPU usage when running `SELECT ... FOR UPDATE` queries on Percona
You can start the stack using Docker Compose with `docker compose up`.
2 DB servers running the [same workload](./repro.php) will be started:
* one is using the `percona` image and consumes more resources than expected
* the other is using the `mysql` image## Flamegraph
On my initial Rocky Linux 9 environment I generated flamegraphes of MySQL and Percona running the same workload.
Percona: ![Flamegraph issue Percona](./flamegraph-percona.svg)
MySQL: ![Flamegraph issue MySQL](./flamegraph-mysql.svg)