From nobody Thu Mar 14 20:58:52 2024 X-Original-To: freebsd-hardware@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 4TwgN275Yqz5Dbg8 for ; Thu, 14 Mar 2024 21:23:14 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4TwgN21zKHz4nKB for ; Thu, 14 Mar 2024 21:23:14 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-doc@fjl.co.uk designates 84.45.41.196 as permitted sender) smtp.mailfrom=freebsd-doc@fjl.co.uk Received: from [127.0.0.1] ([185.69.144.64]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id 42ELNCYH090905 for ; Thu, 14 Mar 2024 21:23:13 GMT (envelope-from freebsd-doc@fjl.co.uk) Date: Thu, 14 Mar 2024 20:58:52 +0000 From: Frank Leonhardt To: freebsd-hardware@freebsd.org Subject: Re: WD Blue 510 SSD and strange write performance User-Agent: K-9 Mail for Android In-Reply-To: <69e47494-01aa-4149-a326-91d82dfdc46e@sentex.net> References: <6504bd49-eca5-4e0a-b2bd-23d29405bb7a@sentex.net> <4832DE6A-5C82-4805-99BB-220D4342AE0F@fjl.co.uk> <69e47494-01aa-4149-a326-91d82dfdc46e@sentex.net> Message-ID: List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.53 / 15.00]; NEURAL_HAM_SHORT(-0.99)[-0.992]; NEURAL_HAM_MEDIUM(-0.98)[-0.976]; NEURAL_HAM_LONG(-0.46)[-0.459]; R_SPF_ALLOW(-0.20)[+ip4:84.45.41.196:c]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:25577, ipnet:84.45.0.0/17, country:GB]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[fjl.co.uk]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hardware@freebsd.org]; RCPT_COUNT_ONE(0.00)[1] X-Rspamd-Queue-Id: 4TwgN21zKHz4nKB Sorry - not that deeply into modern SSD (never written a driver for one), b= ut based on my understanding your TRIM theory makes sense to me=2E I'd try = turning it off=2E It does seem to be an ongoing source of snafus=2E I did use WD Blue SSDs but I suspect they vary quite a bit=2E I've had rat= her too many early failures=2E I wouldn't use them in production but okay f= or Windoze=2E We all know deep down there's a reason the enterprise SSDs co= st what they do :-) I'll keep thinking