Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Apr 2022 17:43:27 +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: Desperate with 870 QVO and ZFS
Message-ID:  <dd9a55ac-053d-7802-169d-04c95c045ed2@FreeBSD.org>
In-Reply-To: <0ef282aee34b441f1991334e2edbcaec@ramattack.net>
References:  <4e98275152e23141eae40dbe7ba5571f@ramattack.net> <665236B1-8F61-4B0E-BD9B-7B501B8BD617@ultra-secure.de> <0ef282aee34b441f1991334e2edbcaec@ramattack.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------xWEDst9IZgYvLPukN2ga6r9b
Content-Type: multipart/mixed; boundary="------------gUL8upCKsfSinXvRen5NU9ab";
 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: <dd9a55ac-053d-7802-169d-04c95c045ed2@FreeBSD.org>
Subject: Re: Desperate with 870 QVO and ZFS
References: <4e98275152e23141eae40dbe7ba5571f@ramattack.net>
 <665236B1-8F61-4B0E-BD9B-7B501B8BD617@ultra-secure.de>
 <0ef282aee34b441f1991334e2edbcaec@ramattack.net>
In-Reply-To: <0ef282aee34b441f1991334e2edbcaec@ramattack.net>

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

Am 06.04.22 um 16:36 schrieb egoitz@ramattack.net:
> Hi Rainer!
>=20
> Thank you so much for your help :) :)
>=20
> Well I assume they are in a datacenter and should not be a power outage=
=2E...
>=20
> About dataset size... yes... our ones are big... they can be 3-4 TB eas=
ily each
> dataset.....
>=20
> We bought them, because as they are for mailboxes and mailboxes grow an=
d
> grow.... for having space for hosting them...

Which mailbox format (e.g. mbox, maildir, ...) do you use?

> We knew they had some speed issues, but those speed issues, we thought =
(as
> Samsung explains in the QVO site) they started after exceeding the spee=
ding
> buffer this disks have. We though that meanwhile you didn't exceed it's=

> capacity (the capacity of the speeding buffer) no speed problem arises.=
 Perhaps
> we were wrong?.

These drives are meant for small loads in a typical PC use case,
i.e. some installations of software in the few GB range, else only
files of a few MB being written, perhaps an import of media files
that range from tens to a few hundred MB at a time, but less often
than once a day.

As the SSD fills, the space available for the single level write
cache gets smaller (on many SSDs, I have no numbers for this
particular device), and thus the amount of data that can be
written at single cell speed shrinks as the SSD gets full.

I have just looked up the size of the SLC cache, it is specified
to be 78 GB for the empty SSD, 6 GB when it is full (for the 2 TB
version, smaller models will have a smaller SLC cache).

But after writing those few GB at a speed of some 500 MB/s (i.e.
after 12 to 150 seconds), the drive will need several minutes to
transfer those writes to the quad-level cells, and will operate
at a fraction of the nominal performance during that time.
(QLC writes max out at 80 MB/s for the 1 TB model, 160 MB/s for the
2 TB model.)

And cheap SSDs often have no RAM cache (not checked, but I'd be
surprised if the QVO had one) and thus cannot keep bookkeeping date
in such a cache, further limiting the performance under load.

And the resilience (max. amount of data written over its lifetime)
is also quite low - I hope those drives are used in some kind of
RAID configuration. 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 ...

--------------gUL8upCKsfSinXvRen5NU9ab--

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

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

wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmJNtR8FAwAAAAAACgkQR+u171r99UQX
jggAh1PLi41CMsG6xbRvf9KA3JRSYjHGSCr3soAi5Su5VZmVNts3ocVUONOfR4yoTj/JGZ0HYvwi
iQm4PxPLS7Fj69joQnernx6Dhem6yg8hJSwrU3HDZQ4lIDSQ2B220+uz9MrqImu21JvDxIRzmgH+
kQ7Q3+ZoxCi0BJX83yL8sh0wMA5tLrV1e8IKrpBR/mLiwQZRoaOPKXKx29eP4Q8St57UySGfGL13
O33jTgM8sAAGkImgAa2JzXRhYQ2KY5QnplYv1cxk6Zbpuq1TgovqGm3pzak0i1kTiK95K3tWYhMh
2ne2gmnXcO6CGu+QeUapXJN10sefE8gRNrBDLzpjJg==
=HKc2
-----END PGP SIGNATURE-----

--------------xWEDst9IZgYvLPukN2ga6r9b--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dd9a55ac-053d-7802-169d-04c95c045ed2>