Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Apr 2022 12:05:42 +0200
From:      Stefan Esser <se@FreeBSD.org>
To:        egoitz@ramattack.net
Cc:        freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org, freebsd-performance@freebsd.org, Rainer Duffner <rainer@ultra-secure.de>
Subject:   Re: {* 05.00 *}Re: Desperate with 870 QVO and ZFS
Message-ID:  <4ef109e8-bd7b-1398-2bc9-191e261d5c06@FreeBSD.org>
In-Reply-To: <e4b7252d-525e-1c0f-c22b-e34b96c1ce83@FreeBSD.org>
References:  <4e98275152e23141eae40dbe7ba5571f@ramattack.net> <665236B1-8F61-4B0E-BD9B-7B501B8BD617@ultra-secure.de> <0ef282aee34b441f1991334e2edbcaec@ramattack.net> <dd9a55ac-053d-7802-169d-04c95c045ed2@FreeBSD.org> <ce51660b5f83f92aa9772d764ae12dff@ramattack.net> <e4b7252d-525e-1c0f-c22b-e34b96c1ce83@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------R8ub0be6TPBsoV0UvSwjPqsv
Content-Type: multipart/mixed; boundary="------------MH3UBEk8xxTm08glzsqFwYDD";
 protected-headers="v1"
From: Stefan Esser <se@FreeBSD.org>
To: egoitz@ramattack.net
Cc: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org,
 freebsd-performance@freebsd.org, Rainer Duffner <rainer@ultra-secure.de>
Message-ID: <4ef109e8-bd7b-1398-2bc9-191e261d5c06@FreeBSD.org>
Subject: Re: {* 05.00 *}Re: Desperate with 870 QVO and ZFS
References: <4e98275152e23141eae40dbe7ba5571f@ramattack.net>
 <665236B1-8F61-4B0E-BD9B-7B501B8BD617@ultra-secure.de>
 <0ef282aee34b441f1991334e2edbcaec@ramattack.net>
 <dd9a55ac-053d-7802-169d-04c95c045ed2@FreeBSD.org>
 <ce51660b5f83f92aa9772d764ae12dff@ramattack.net>
 <e4b7252d-525e-1c0f-c22b-e34b96c1ce83@FreeBSD.org>
In-Reply-To: <e4b7252d-525e-1c0f-c22b-e34b96c1ce83@FreeBSD.org>

--------------MH3UBEk8xxTm08glzsqFwYDD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Am 06.04.22 um 23:49 schrieb Stefan Esser:
> Am 06.04.22 um 18:34 schrieb egoitz@ramattack.net:
>=20
>>> The 870 QVO is specified for 370 full capacity
>>> writes, i.e. 370 TB for the 1 TB model. That's still a few hundred
>>> GB a day - but only if the write amplification stays in a reasonable
>>> range ...
>>> =C2=A0
>>> *Well yes... 2880TB in our case....not bad.. isn't it?*
>=20
> I assume that 2880 TB is your total storage capacity? That's not too ba=
d, in
> fact. ;-)

I just noticed that this is not the extreme total size of a ZFS pool
(should have noticed this while answering late at night ...)

And no, a specified life-time of 2880 TB written is not much, it is
at the absolute lower end of currently available SSDs at 360 TB per
1 TB of capacity.

This is equivalent to 360 total capacity writes, but given the high
amount of write amplification that can be assumed to occur in your
use case, I'd heavily over-provision a system with such SSDs ...
(or rather: strictly avoid them in a non-consumer setting).

--------------MH3UBEk8xxTm08glzsqFwYDD--

--------------R8ub0be6TPBsoV0UvSwjPqsv
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmJOt3YFAwAAAAAACgkQR+u171r99USG
4AgAqvLdjcqRhYzJHDNPIR+8TN0JKwMia2AI7dwFi/edSRFtjP50d/sbgxhP7xkf6a13LuLypubc
UK2ldNCHlczP/9m5+uG2MTb9E24Pc1bpX4o459oFzx7MGRyRksMmMKnNyidiVIx4W/ihfZa0b/5K
ICbgTmE79RIc3tX8cn77Kp8W8asjABCE2vgqTLtyJpfuhBSg60flkjMAOoBwsyXDNKvEDWWuR3zU
U4kxS00DZ2Cb8EHMmi5yiyH+GqoJWRH55BYl0bw3ppDubbQuEZWJojcMZ2eWFJYcC29LkYvCUDrc
YgesfZGPQ9eTk1cbKq01ZOCk4zOsgt2PcmFla759oQ==
=GJ82
-----END PGP SIGNATURE-----

--------------R8ub0be6TPBsoV0UvSwjPqsv--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ef109e8-bd7b-1398-2bc9-191e261d5c06>