Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> writes: > On Mon, 4 Dec 2023 15:49:02 -0800 Stefan Roesch <shr@xxxxxxxxxxxx> wrote: > >> What is the KSM advisor? >> ========================= >> The ksm advisor automatically manages the pages_to_scan setting to >> achieve a target scan time. The target scan time defines how many seconds >> it should take to scan all the candidate KSM pages. In other words the >> pages_to_scan rate is changed by the advisor to achieve the target scan >> time. > > Dumb question time. Can this be done in userspace? Presumably this > will require exposing some additional kernel state to userspace. > Userspace doesn't look like a good fit - We need access to how much cpu the ksmd kernel thread spent during the last scan - We want to recompute this after each scan completes, so the new parameter is in effect for the next scan and to avoid we have to partially deal with new values in the middle - When the advisor is active we want to disable that other users can manually set the scan rate. The scan advisor might be augmented with per page cost in the future. >> Why do we need a KSM advisor? >> ============================== >> The number of candidate pages for KSM is dynamic. It can often be observed >> that during the startup of an application more candidate pages need to be >> processed. Without an advisor the pages_to_scan parameter needs to be >> sized for the maximum number of candidate pages. With the scan time >> advisor the pages_to_scan parameter based can be changed based on demand. >> >> Algorithm >> ========== >> The algorithm calculates the change value based on the target scan time >> and the previous scan time. To avoid pertubations an exponentially >> weighted moving average is applied. >> >> The algorithm has a max and min >> value to: >> - guarantee responsiveness to changes >> - to limit CPU resource consumption >> >> Parameters to influence the KSM scan advisor >> ============================================= >> The respective parameters are: >> - ksm_advisor_mode >> 0: None (default), 1: scan time advisor >> - ksm_advisor_target_scan_time >> how many seconds a scan should of all candidate pages take >> - ksm_advisor_max_cpu >> upper limit for the cpu usage in percent of the ksmd background thread >> >> The initial value and the max value for the pages_to_scan parameter can >> be limited with: >> - ksm_advisor_min_pages >> minimum value for pages_to_scan per batch >> - ksm_advisor_max_pages >> maximum value for pages_to_scan per batch > > Should these be called ksm_advisor_min_pages_to_scan? > That's a good recommendation. I'll make that change and the corresponding change for max. >> The default settings for the above two parameters should be suitable for >> most workloads. >> >> The parameters are exposed as knobs in /sys/kernel/mm/ksm. By default the >> scan time advisor is disabled. > > Disabling it will reduce the effectiveness of testing. What are the > risks of defaulting to "on"? > Some users might have already tuned the values for pages_to_scan. So generally turning it on might not be good. However we could turn it on, it the default value of 100 for pages_to_scan hasn't been changed. Any thoughts? >> Currently there are two advisors: >> - none and >> - scan-time. >> >> Resource savings >> ================= >> Tests with various workloads have shown considerable CPU savings. Most >> of the workloads I have investigated have more candidate pages during >> startup. Once the workload is stable in terms of memory, the number of >> candidate pages is reduced. Without the advisor, the pages_to_scan needs >> to be sized for the maximum number of candidate pages. So having this >> advisor definitely helps in reducing CPU consumption. >> >> For the instagram workload, the advisor achieves a 25% CPU reduction. > > 25% of what? What is the overall affect on machine resource > consumption? > 25% of the cpu consumption of the ksmd background thread. On a 32 cpu machine this translates to 1 to 2% cpu savings alltogether. However this is highly workload dependent. >> Once the memory is stable, the pages_to_scan parameter gets reduced to >> about 40% of its max value. >> >> The new advisor works especially well if the smart scan feature is also >> enabled. >> >> How is defining a target scan time better? >> =========================================== >> For an administrator it is more logical to set a target scan time.. The >> administrator can determine how many pages are scanned on each scan. >> Therefore setting a target scan time makes more sense. >> >> In addition the administrator might have a good idea about the memory >> sizing of its respective workloads. >> >> Setting cpu limits is easier than setting The pages_to_scan parameter. The >> pages_to_scan parameter is per batch. For the administrator it is difficult >> to set the pages_to_scan parameter. >> >> Tracing >> ======= >> A new tracing event has been added for the scan time advisor. The new >> trace event is called ksm_advisor. It reports the scan time, the new >> pages_to_scan setting and the cpu usage of the ksmd background thread. >> >> Other approaches >> ================= >> >> Approach 1: Adapt pages_to_scan after processing each batch. If KSM >> merges pages, increase the scan rate, if less KSM pages, reduce the >> the pages_to_scan rate. This doesn't work too well. While it increases >> the pages_to_scan for a short period, but generally it ends up with a >> too low pages_to_scan rate. >> >> Approach 2: Adapt pages_to_scan after each scan. The problem with that >> approach is that the calculated scan rate tends to be high. The more >> aggressive KSM scans, the more pages it can de-duplicate. >> >> There have been earlier attempts at an advisor: >> propose auto-run mode of ksm and its tests >> (https://marc.info/?l=linux-mm&m=166029880214485&w=2)
