| Bug #55171 | How much sort_buffer_size are actually used? | ||
|---|---|---|---|
| Submitted: | 12 Jul 2010 7:32 | ||
| Reporter: | Mikiya Okuno | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Performance Schema | Severity: | S4 (Feature request) |
| Version: | OS: | Any | |
| Assigned to: | Marc ALFF | CPU Architecture: | Any |
[12 Jul 2010 7:32]
Mikiya Okuno
[15 Jul 2010 19:39]
Peter Gulutzan
Perhaps we'd want (global and/or local)
current + maximum i.e. high water mark +
number of times overflow or eviction happened,
for a lot of variables that have sizes
("show variables like '%size';" gives an indication).
It's the sort of thing we used to do with
SHOW STATUS, but indeed a performance_schema
table might be more appropriate.
