From nobody Fri Nov 15 16:40:17 2024 X-Original-To: freebsd-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 4XqjSH4QK3z5dLJR for ; Fri, 15 Nov 2024 16:40:31 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XqjSH2YFHz4L2b for ; Fri, 15 Nov 2024 16:40:31 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f50.google.com with SMTP id 4fb4d7f45d1cf-5cf8ef104a8so1323281a12.2 for ; Fri, 15 Nov 2024 08:40:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731688830; x=1732293630; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+0AgpAKC2QZggRLZ63vmn6oaJBhQvUwHH2FtfV+b27w=; b=H8eC0G7vgr+MO4q5AgnmfT3M6Gaaa5Ty9A0Pl0J7YBCsV7jTmhuNFFJCUDxmXMFPpg XDbTZPJt1WIu8vEf5xwBkcV18nL/54Rbq22JsfMtwFg23547QwUsWahMgKj3dzY4JVOm hKZgufqkWWVNOpBqEZoER6ZCRjFkVEnGb5qzsJD7UX8UqvN3wD5OI0dCJd7Ha2jImfm1 K+ZANBHecOZeF7FWlZKobBwduR9rJd3cly0UANbixQ1stHoYUPwURvhh14EIloyqjXdf 3dTTalC1uSBG0Aa3dbGyDpcVEa/pUSKw3zRf6uJ2txT3jEbmhdGhs0RuW8oxCaEanng+ q98w== X-Gm-Message-State: AOJu0YzyhAHyskF5+WtzE1jNTL+yRJPwwEf/JpjZf+NLK0ll3oYYWSQQ xKRWNkLaPLkoNFz/jshfuZaIKZBcGoFijhU4jOKOkmpbjp3ITrDmozOOQ3577uY/lxGZUoQckjk pmK++JavPMd4voIyje1CZ0a0PsP8eBg== X-Google-Smtp-Source: AGHT+IEkMPrO9VZcAhNiDO3DYGnP43KXMxi0AQN9L6ZJyk4duy1fvNefeeZX0gDCSfgzUzIme0fiNmeCGYBZjTyvgm4= X-Received: by 2002:a05:6402:2807:b0:5cf:8449:e757 with SMTP id 4fb4d7f45d1cf-5cf8fc8b6d8mr2491859a12.13.1731688829608; Fri, 15 Nov 2024 08:40:29 -0800 (PST) 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 References: In-Reply-To: From: Alan Somers Date: Fri, 15 Nov 2024 09:40:17 -0700 Message-ID: Subject: Re: improving nfs client & server performance To: infoomatic Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4XqjSH2YFHz4L2b X-Spamd-Bar: ---- On Fri, Nov 15, 2024 at 9:34=E2=80=AFAM infoomatic wrot= e: > > From my personal experience, regarding the usage with ZFS: > > * SMR disks are are absolutely to avoid, their performance is horrible. > * QLC SSD disks are also horrible in performance - after a short burst > of performance they go back to spindling rust disks performance To be clear, SMR disk performance is horrible ***on file systems that weren't designed for them***. That is to say, on every single legacy file system. Samsung claims to fully support SMR disks on F2FS, but that's an overwriting file system. Microsoft claims to fully support SMR disks on ReFS. But look more closely, and you'll see that not all features are supported there. So I'm not aware of any CoW file system that fully supports SMR. Any, that is, except for the one I wrote myself. Alas, I don't have funding to finish it to a production-ready state ...