| Bug #120596 | WAIT_FOR_READ, WAIT_FOR_WRITE is stuck in the 2012 | ||
|---|---|---|---|
| Submitted: | 2 Jun 6:37 | ||
| Reporter: | Alex Zimnitski | Email Updates: | |
| Status: | Open | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 8.0.46, 8.4.9 | OS: | Linux |
| Assigned to: | CPU Architecture: | x86 | |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.047 sec. using MySQL 8.4.5-u11-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2026, Oracle Corporation and/or its affiliates
Description: This constant does match NVMe read response times (100 us) but NVMe can do reads in ~10 us. constexpr std::chrono::microseconds WAIT_FOR_READ{100}; constexpr std::chrono::microseconds WAIT_FOR_WRITE{100}; It is used in buf_page_get_zip, zip_page_handler, check_state How to repeat: Run Innodb on NVMe storage Suggested fix: Use a shorter wait