You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[BP] MB-59368: Use getPageableMemCurrent/MemLowWatermark in PagingVisitor
The MB highlighted that for ephemeral auto_delete, paging can be
triggered as the trigger uses getPageableMemCurrent/MemLowWatermark
but the PagingVisitor immediately cancels paging because it compared
getEstimatedTotalMemoryUsed vs stats.mem_low_wat, nothing is freed
and paging is immediately triggered to run again - resulting in a
noticeable increase in CPU but no memory reduction.
Commit changes PagingVisitor to use the Pageable functions when
deciding to stop, memory is now released and no further paging is
triggered.
Conflicts:
engines/ep/src/paging_visitor.cc
engines/ep/tests/module_tests/item_pager_test.cc
Not a clean backport and required some dependent test-code backporting.
Change-Id: Ic83764c693cc35d4e0cc9b36c7aae8cb98e4bb30
Reviewed-on: https://review.couchbase.org/c/kv_engine/+/201918
Reviewed-by: Dave Rigby <[email protected]>
Well-Formed: Restriction Checker
Tested-by: Dave Rigby <[email protected]>
0 commit comments