On Mon, Feb 17, 2020 at 09:23:52PM +0800, ?????? wrote: > > > On 2020/2/17 ??????7:58, Mel Gorman wrote: > [snip] > >> Mel, I suspect you still feel that way, right? > >> > > > > Yes, I still think it would be a struggle to interpret the data > > meaningfully without very specific knowledge of the implementation. If > > the scan rate was constant, it would be easier but that would make NUMA > > balancing worse overall. Similarly, the stat might get very difficult to > > interpret when NUMA balancing is failing because of a load imbalance, > > pages are shared and being interleaved or NUMA groups span multiple > > active nodes. > > Hi, Mel, appreciated to have you back on the table :-) > > IMHO the scan period changing should not be a problem now, since the > maximum period is defined by user, so monitoring at maximum period > on the accumulated page accessing counters is always meaningful, correct? > It has meaning but the scan rate drives the fault rate which is the basis for the stats you accumulate. If the scan rate is high when accesses are local, the stats can be skewed making it appear the task is much more local than it may really is at a later point in time. The scan rate affects the accuracy of the information. The counters have meaning but they needs careful interpretation. > FYI, by monitoring locality, we found that the kvm vcpu thread is not > covered by NUMA Balancing, whatever how many maximum period passed, the > counters are not increasing, or very slowly, although inside guest we are > copying memory. > > Later we found such task rarely exit to user space to trigger task > work callbacks, and NUMA Balancing scan depends on that, which help us > realize the importance to enable NUMA Balancing inside guest, with the > correct NUMA topo, a big performance risk I'll say :-P > Which is a very interesting corner case in itself but also one that could have potentially have been inferred from monitoring /proc/vmstat numa_pte_updates or on a per-task basis by monitoring /proc/PID/sched and watching numa_scan_seq and total_numa_faults. Accumulating the information on a per-cgroup basis would require a bit more legwork. > Maybe not a good example, but we just try to highlight that NUMA Balancing > could have issue in some cases, and we want them to be exposed, somehow, > maybe by the locality. > Again, I'm somewhat neutral on the patch simply because I would not use the information for debugging problems with NUMA balancing. I would try using tracepoints and if the tracepoints were not good enough, I'd add or fix them -- similar to what I had to do with sched_stick_numa recently. The caveat is that I mostly look at this sort of problem as a developer. Sysadmins have very different requirements, especially simplicity even if the simplicity in this case is an illusion. -- Mel Gorman SUSE Labs
