From nobody Sun Jan 14 14:30:44 2024 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TCd3n5ly6z56J0v for ; Sun, 14 Jan 2024 14:30:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TCd3n4Hh4z3yp2 for ; Sun, 14 Jan 2024 14:30:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705242645; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4EvB6kckQb25tWXR/lYv48Oo4NNRZSq8dk8/5SgJ6tI=; b=a6adSDXyijGIJzJe5YUFaPS/o2pmZ8N9ESXardv1KYJU5vMEp9GACj4U2ItDLP6oszCDEV 1KADYuqYrpq4ovo9nKB8bn0CghS0ukK0wZ3y7q40KHcXiD+IIOnZFcTieIYYBTrKdDwVP9 5lIEvpdqtxnMewcH8wugqUieUl5NBWwDX3DdXVniBNBQDegVQYznTjIP6sIUz+DHaGWNv6 g69zDTF28a/yKAKSc8Mb75S2/y73hKBAfv9eXQs73oaKxblmLhoeoPLkGTjys8g4eFL+tW 006tQLSr3MeQ4LRDjli1FWpkr0eU51pdbnXJHJuBqs9ZnINv0BDUDRsUzrC54A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705242645; a=rsa-sha256; cv=none; b=SF1y3MLORdsKeP5VcQd2J45mg5Ffan0t40o23PFVC/MjVahQG50VJC+4heMNRMsSm7W227 YWduLDAps/26c7IJp07iA5Eq39O5Dl9qFFU/U1MxIyi3X20uCz8DyJ85APwZe2iXjkjNoj SacfLYw9PIRBfqhvRT5J/QJT1HFPZCXTv1W5K/cI6jENw9wTxLK65kkdm3i+FKBaaWCC3r yNsK9ER9jHuUdmxbIYZVfBCxHw54YlN3tB2V9cTRdvfW3C6DrwOHTpx+yRbkeXQ4VSuohV vpZo4q4edhoEGVROo2F1uIRoZ5X1s0m5Idzr/ueHW52pOo2LL5Pw5RvTlHEi2w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4TCd3n3M94zHBN for ; Sun, 14 Jan 2024 14:30:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 40EEUj6k044366 for ; Sun, 14 Jan 2024 14:30:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 40EEUjxD044339 for fs@FreeBSD.org; Sun, 14 Jan 2024 14:30:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 276299] Write performance to NFS share is ~4x slower than on 13.2 Date: Sun, 14 Jan 2024 14:30:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.0-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276299 --- Comment #12 from Rick Macklem --- If you are playing with network related stuff, here's a bit more (no pun intended;-). Look at any stats generated by both server and client NIC drivers for errors, etc. If you have a different NIC lying about, particularily if it has a different chipset in it, try it. Look for a tunable in the NIC driver that adjusts interrupt moderation. Interrupt moderation is good for streaming traffic, not so good for NFS. Once a NFS client sends an RPC message, it waits for a response. Any delay in the reply, slows it down and interrupt moderation can delay the interrupt and, therefore, the RPC reply. And don't forget simple stuff like cables. They can get damaged at any time. Good luck with it, rick --=20 You are receiving this mail because: You are the assignee for the bug.=