From owner-freebsd-hackers@freebsd.org Thu Jun 4 13:44:07 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0863E2F3ECC for ; Thu, 4 Jun 2020 13:44:07 +0000 (UTC) (envelope-from gbergling@gmail.com) Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com [IPv6:2a00:1450:4864:20::342]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49d6Sk4mRrz3b6S; Thu, 4 Jun 2020 13:44:06 +0000 (UTC) (envelope-from gbergling@gmail.com) Received: by mail-wm1-x342.google.com with SMTP id c71so5284147wmd.5; Thu, 04 Jun 2020 06:44:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=Y0mGJ2fA3s1Ce+rcx9TBjzGZUNRApfRGZTUZ4dW9ZRY=; b=hz/w0LniivpCxgUW/Uk9FA5S7aqu/molwuMmQIoNeIVoW7bsSm/tt+u7PPnfYiBLh0 jckcz96uJrY/qKKG4Y5NE0tXbZko2XkEFTiegyV5Vh6DaWRfHZ5gXo+FyCE9I71v5HYe MHA76MI0BOqxO3dER43ggvCjnxHvZ1mNvPOj6bWWPmfhJ+17sdxKESNYdyAzSPJnWeMX c3kjuV5DHdfFygo3GW7kBZ2GfLTCDNBcwVJj/NBCI/9KVXURDOQD9kWDw6cHa0n3kJpa +GUnwNb2sgr/b36AVaW2/6ozx8zSnvzIeS8xm7zmF9w6Qwiy0HMhdn4P/jucx34fKfRY 02zQ== X-Gm-Message-State: AOAM533VoaFREY4J9gUuWFzAxdtJGOXPEQj3eP79gO3gwUKzFHbzopeT ILgfl9KH3LX8RVo1kfpcNEvwg3TH1aw= X-Google-Smtp-Source: ABdhPJx00JnwyggGkwZ9taDcQkIFbf45Bi8EGkiyKzAdYuxt6JAmA6bDsObSGyfofHfKdKK6C+OgPA== X-Received: by 2002:a05:600c:2c51:: with SMTP id r17mr3865000wmg.147.1591278244406; Thu, 04 Jun 2020 06:44:04 -0700 (PDT) Received: from lion.0xfce3.net (p4fd3af72.dip0.t-ipconnect.de. [79.211.175.114]) by smtp.gmail.com with ESMTPSA id i3sm8124352wrm.83.2020.06.04.06.44.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Jun 2020 06:44:03 -0700 (PDT) Sender: Gordon Bergling Date: Thu, 4 Jun 2020 15:44:02 +0200 From: Gordon Bergling To: Ian Lepore Cc: Gordon Bergling , freebsd-hackers@freebsd.org, Allan Jude Subject: Re: Constant load of 1 on a recent 12-STABLE Message-ID: <20200604134402.GA63434@lion.0xfce3.net> References: <20200603101607.GA80381@lion.0xfce3.net> <20200603202929.GA65032@lion.0xfce3.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: X-Operating-System: FreeBSD 12.1-STABLE amd64 X-Host-Uptime: 3:36PM up 1 day, 8:18, 3 users, load averages: 4.53, 4.76, 4.79 X-Rspamd-Queue-Id: 49d6Sk4mRrz3b6S X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 13:44:07 -0000 Hi Ian, On Wed, Jun 03, 2020 at 02:40:07PM -0600, Ian Lepore wrote: > On Wed, 2020-06-03 at 22:29 +0200, Gordon Bergling via freebsd-hackers wrote: > > [...] > > > > The only key performance indicator that is relatively high IMHO, for a > > non-busy system, are the context switches, that vmstat has reported. > > > > ------------------------------------------------------------------------------- > > procs memory page disks faults cpu > > r b w avm fre flt re pi po fr sr da0 da1 in sy cs us sy id > > 0 0 0 514G 444M 7877 2 7 0 9595 171 0 0 0 4347 43322 17 2 81 > > 0 0 0 514G 444M 1 0 0 0 0 44 0 0 0 121 40876 0 0 100 > > 0 0 0 514G 444M 0 0 0 0 0 40 0 0 0 133 42520 0 0 100 > > 0 0 0 514G 444M 0 0 0 0 0 40 0 0 0 120 43830 0 0 100 > > 0 0 0 514G 444M 0 0 0 0 0 40 0 0 0 132 42917 0 0 100 > > -------------------------------------------------------------------------------- > > > > Any other ideas what could generate that load? > > Interrupts/second consistently zero is the strange part of that vmstat > output. That makes me think the problem has something to do with > timekeeping and is a problem with the statistics used by top rather > than having some "stuck process" actually consuming time. > > Are there any other signs of timekeeping trouble on the machine, like > ntpd repeatedly stepping the clock? What's the output for > > sysctl kern.timecounter > sysctl kern.eventtimer first, sorry for the late response. The e-mail went into my spam folder. There aren't any timekeeping problemes on that machine. The requested output of the request sysctl trees are the following: ------------------------------------------------------------------------------- $ sysctl kern.timecounter kern.timecounter.tsc_shift: 1 kern.timecounter.smp_tsc_adjust: 0 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 0 kern.timecounter.fast_gettime: 1 kern.timecounter.tick: 1 kern.timecounter.choice: ACPI-fast(900) Hyper-V-TSC(3000) TSC-low(-100) Hyper-V(2000) dummy(-1000000) kern.timecounter.hardware: Hyper-V-TSC kern.timecounter.alloweddeviation: 5 kern.timecounter.timehands_count: 2 kern.timecounter.stepwarnings: 0 kern.timecounter.tc.ACPI-fast.quality: 900 kern.timecounter.tc.ACPI-fast.frequency: 3579545 kern.timecounter.tc.ACPI-fast.counter: 483840041 kern.timecounter.tc.ACPI-fast.mask: 4294967295 kern.timecounter.tc.Hyper-V-TSC.quality: 3000 kern.timecounter.tc.Hyper-V-TSC.frequency: 10000000 kern.timecounter.tc.Hyper-V-TSC.counter: 1283654243 kern.timecounter.tc.Hyper-V-TSC.mask: 4294967295 kern.timecounter.tc.TSC-low.quality: -100 kern.timecounter.tc.TSC-low.frequency: 1600955785 kern.timecounter.tc.TSC-low.counter: 1215462580 kern.timecounter.tc.TSC-low.mask: 4294967295 kern.timecounter.tc.Hyper-V.quality: 2000 kern.timecounter.tc.Hyper-V.frequency: 10000000 kern.timecounter.tc.Hyper-V.counter: 1283862164 kern.timecounter.tc.Hyper-V.mask: 4294967295 ------------------------------------------------------------------------------- and ------------------------------------------------------------------------------- $ sysctl kern.eventtimer kern.eventtimer.periodic: 0 kern.eventtimer.timer: LAPIC kern.eventtimer.idletick: 0 kern.eventtimer.singlemul: 4 kern.eventtimer.choice: Hyper-V(1000) LAPIC(100) RTC(0) kern.eventtimer.et.Hyper-V.quality: 1000 kern.eventtimer.et.Hyper-V.frequency: 10000000 kern.eventtimer.et.Hyper-V.flags: 6 kern.eventtimer.et.RTC.quality: 0 kern.eventtimer.et.RTC.frequency: 32768 kern.eventtimer.et.RTC.flags: 17 kern.eventtimer.et.LAPIC.quality: 100 kern.eventtimer.et.LAPIC.frequency: 100426660 kern.eventtimer.et.LAPIC.flags: 15 ------------------------------------------------------------------------------- I hope you see something unusual that could be changed to solve the problem. Kind regards, Gordon -- Gordon Bergling Mobile: +49 170 23 10 948 Web: https://www.gordons-perspective.com/ Mail: gbergling@gmail.com Think before you print!