-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
ASeasonTooMany-2023-08-22, BermudaTriangle- 2023-09-05, TheMoon-StorEng - 2023-09-19, NachoCheese - 2023-10-03, Joker - StorEng - 2023-10-17, Asparagus-StorEng - 2023-10-31, c(3x10^8)-StorEng - 2023-11-14, 2023-11-28 - Anthill Tiger, 2023-12-12 - Heisenbug
-
3
-
Triage and Release
-
There are a set of statistics that track block compression ratio - it was observed that they are always set to 0, even when pages are clearly being compressed. For example:
"compressed pages written" : 110204, "number of blocks with compress ratio greater than 64" : 0, "number of blocks with compress ratio smaller than 16" : 0, "number of blocks with compress ratio smaller than 2" : 0, "number of blocks with compress ratio smaller than 32" : 0, "number of blocks with compress ratio smaller than 4" : 0, "number of blocks with compress ratio smaller than 64" : 0, "number of blocks with compress ratio smaller than 8" : 0, "page written failed to compress" : 1581, "page written was too small to compress" : 1077
It appears as though the change for WT-6022, where a call to wt_stat_compr_ratio_hist_incr was replaced with a macro (WT_STAT_COMPR_RATIO_HIST_INCR_FUNC) that doesn't appear to be used.
We should fix the code to increment the statistics again, and also add a test to ensure we don't break them again.