Details
-
Task
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
For axel for https://github.com/MariaDB/server/pull/1956#issuecomment-984543127
While we are at it: can we have some diagnostics on buffer pool allocation please? And also use some more meaningful units for the different sizes. Instead of this:
[Note] InnoDB: Initializing buffer pool, total size = 17179869184, chunk size = 134217728
|
[Note] InnoDB: Completed initialization of buffer pool
|
I would like to see:
[Note] InnoDB: Initializing buffer pool, total size = 16384MB, chunk size = 128MB
|
[Note] InnoDB: Allocating buffer pool with page size = 2048KB
|
[Note] InnoDB: Completed initialization of buffer pool
|
Buffer pool size and chunk size could use MB and fall back to KB in case they are very small. Page size can be given in KB.
Attachments
Issue Links
- relates to
-
MDEV-25652 Add support for SI suffixes in SET statement for configuring size-related variables
-
- Open
-
-
MDEV-27314 Buffer pool resize output: 14 minor typo/capitalization/uniformity/wording updates
-
- Closed
-
-
-
- Closed
-
-
-
- Open
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to MDEV-25652 [ MDEV-25652 ] |
| Workflow | MariaDB v3 [ 128093 ] | MariaDB v4 [ 131608 ] |
| Fix Version/s | 10.8 [ 26121 ] | |
| Fix Version/s | 10.7 [ 24805 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Testing [ 10301 ] |
| Assignee | Daniel Black [ danblack ] |
| Assignee | Roel Van de Paar [ roel ] |
This seems only partially implemented (page size missing)?
|
10.8.0 preview-10.8-MDEV-14425-innodb 23849209738153bed4ea60f39830305840ee4025 (Debug) |
2021-12-20 5:18:54 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
|
2021-12-20 5:18:54 0 [Note] InnoDB: Completed initialization of buffer pool
|
danblack Could you please add an MTR test that does a buffer pool resize and also check the output of the same, i.e. potentially that output may be updated as well? Vice versa, we could also add unit size here to align with buffer pool resize output?) Ref MDEV-27314
| Assignee | Roel Van de Paar [ roel ] | Daniel Black [ danblack ] |
| Link |
This issue relates to |
| Summary | humanize the bytes in innodb info/error messages | Humanize the number of bytes in InnoDB buffer pool messages |
| Summary | Humanize the number of bytes in InnoDB buffer pool messages | Humanize the number of bytes in InnoDB messages |
The tree
|
origin/bb-10.8-MDEV-14425 614e46b89ffe7357e5b72ea0d0fd3f490567a384 2022-01-13T20:32:56+02:00
|
contains the modifications made by MDEV-27158 and behaved well in RQG testing.
|
Bad effects observed exist in the main trees too or are known and caused by other MDEVs.
|
Please note that the RQG tests do not check if the MDEV-27158 specification is followed.
|
| Fix Version/s | 10.8.1 [ 26815 ] | |
| Fix Version/s | 10.8 [ 26121 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Testing [ 10301 ] | Closed [ 6 ] |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-35498 [ MDEV-35498 ] |
Please see my comment in MDEV-25652. I don’t think that we should abuse decimal multiplier names like k, M, G, T (10³, 10⁶, 10⁹, 10¹²) for binary ones (2¹⁰, 2²⁰, 2³⁰, 2⁴⁰). RAM is usually measured in powers of 1024 (2¹⁰) octets or bits. We should use units like KiB, MiB, GiB, TiB.