Stone memory leak in commit record bitmap caching
There is a slow C heap memory leak in the handling of bitmap caching for commit records. This can be observed by monitoring the stone statistic BmCHeapPages. The rate of increase is proportional to the number of commits performed (stone statistic TotalCommits).
Workaround
Disable the mechanism by setting in the stone config file:
STN_COMMIT_RECORD_BM_CACHING = FALSE;
Impacts on the setting are outlined in the config file comment:
# STN_COMMIT_RECORD_BM_CACHING
# When true, enables caching at the commit point of page allocation
# information needed when disposing a commit record.
# This can reduce I/Os during commit record dispose when the commit record
# backlog is high, or when there is a lot of page preemption occurring
# in the shared cache.
# When enabled, the maximum commit rate is slightly lower
# and commit latency is slightly higher because more work is done in
# the commit critical region in stone.
Last updated: 7/5/18