On Thu, Jul 04, 2019 at 08:32:06AM +0800, Huang, Ying wrote: > Mel Gorman <mgorman@xxxxxxx> writes: > > > On Tue, Jun 25, 2019 at 09:23:22PM +0800, huang ying wrote: > >> On Mon, Jun 24, 2019 at 10:25 PM Mel Gorman <mgorman@xxxxxxx> wrote: > >> > > >> > On Mon, Jun 24, 2019 at 10:56:04AM +0800, Huang Ying wrote: > >> > > The autonuma scan period should be increased (scanning is slowed down) > >> > > if the majority of the page accesses are shared with other processes. > >> > > But in current code, the scan period will be decreased (scanning is > >> > > speeded up) in that situation. > >> > > > >> > > This patch fixes the code. And this has been tested via tracing the > >> > > scan period changing and /proc/vmstat numa_pte_updates counter when > >> > > running a multi-threaded memory accessing program (most memory > >> > > areas are accessed by multiple threads). > >> > > > >> > > >> > The patch somewhat flips the logic on whether shared or private is > >> > considered and it's not immediately obvious why that was required. That > >> > aside, other than the impact on numa_pte_updates, what actual > >> > performance difference was measured and on on what workloads? > >> > >> The original scanning period updating logic doesn't match the original > >> patch description and comments. I think the original patch > >> description and comments make more sense. So I fix the code logic to > >> make it match the original patch description and comments. > >> > >> If my understanding to the original code logic and the original patch > >> description and comments were correct, do you think the original patch > >> description and comments are wrong so we need to fix the comments > >> instead? Or you think we should prove whether the original patch > >> description and comments are correct? > >> > > > > I'm about to get knocked offline so cannot answer properly. The code may > > indeed be wrong and I have observed higher than expected NUMA scanning > > behaviour than expected although not enough to cause problems. A comment > > fix is fine but if you're changing the scanning behaviour, it should be > > backed up with data justifying that the change both reduces the observed > > scanning and that it has no adverse performance implications. > > Got it! Thanks for comments! As for performance testing, do you have > some candidate workloads? > Ordinarily I would hope that the patch was motivated by observed behaviour so you have a metric for goodness. However, for NUMA balancing I would typically run basic workloads first -- dbench, tbench, netperf, hackbench and pipetest. The objective would be to measure the degree automatic NUMA balancing is interfering with a basic workload to see if they patch reduces the number of minor faults incurred even though there is no NUMA balancing to be worried about. This measures the general overhead of a patch. If your reasoning is correct, you'd expect lower overhead. For balancing itself, I usually look at Andrea's original autonuma benchmark, NAS Parallel Benchmark (D class usually although C class for much older or smaller machines) and spec JBB 2005 and 2015. Of the JBB benchmarks, 2005 is usually more reasonable for evaluating NUMA balancing than 2015 is (which can be unstable for a variety of reasons). In this case, I would be looking at whether the overhead is reduced, whether the ratio of local hits is the same or improved and the primary metric of each (time to completion for Andrea's and NAS, throughput for JBB). Even if there is no change to locality and the primary metric but there is less scanning and overhead overall, it would still be an improvement. If you have trouble doing such an evaluation, I'll queue tests if they are based on a patch that addresses the specific point of concern (scan period not updated) as it's still not obvious why flipping the logic of whether shared or private is considered was necessary. -- Mel Gorman SUSE Labs
