9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Riddler <riddler876@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Throwing in the Towel
Date: Sun, 26 May 2024 22:20:16 +0100	[thread overview]
Message-ID: <CAGMcHPofuW1Qhf4-9bAugUDB8B-wvdqgzOrCg4JUf655JSFNDg@mail.gmail.com> (raw)
In-Reply-To: <17167523800.5BBf3dBb0.7751@composer.9fans.topicbox.com>

[-- Attachment #1: Type: text/plain, Size: 2345 bytes --]

Back of the napkin:

venti(8) has an index entry as 40 bytes. That would fill a 1MB erasure
block in 25k writes. A SLC should handle at least twice that. A MLC is
probably less than half that from what I understand. But we haven't
discussed wear levelling yet. With the index recommended to be 5% of the
data size there should be plenty of data blocks with write cycles left for
the SSD to wear level with. I wouldn't worry about it.

The 128MB case however is pretty bad. It'll take 3,200k writes. Given the
data blocks, following the 4k assumption from the manual, will fill a 128MB
block in 32k writes that could kill a  cheap low write capacity SSD just
with the data blocks.

My cursory conclusion; back of the napkin, index behaviour is not ideal but
shouldn't cause any issues for regular wear levelling SSD (which is all of
them now right?) with a few MB erasure blocks. But going beyond that size
and yeah... Ouch.

But that's just small index updates and large erasure block SSDs for you.
Transactional databases doing lots of small updates are also known for
being able to kill SSDs. As I understand it common practice is to over
provision a transactional database SSD to make up for it.


On Sun, 26 May 2024, 20:40 , <wb.kloke@gmail.com> wrote:

> I would like to refresh my questions from may 4th.
>
> Can it be the case that the venti index file exhibits a desastrous write
> pattern for SSDs?
>
> I presume that each new block written to venti  causes a random block to
> be rewritten in the index file, until the bucket is full (after 215
> writes). Given, that the erasure blocks in the SSD may be of size 1MB or
> even 128MB, each such write may be a big strain on the device.
>
> Any opinions?
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/T2ca67486c7a13a77-M45995ae775e5ed31efd6cdb6>
>

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2ca67486c7a13a77-Mccab748b1a801a2849a72e6e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3084 bytes --]

  reply	other threads:[~2024-05-26 21:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 15:13 Steven Stallion
2024-05-04 19:16 ` [9fans] Plan9 wept! - " Alexandr Babic
2024-05-04 20:21 ` [9fans] " Shawn Rutledge
2024-05-04 20:37   ` wb.kloke
2024-05-26 19:39     ` wb.kloke
2024-05-26 21:20       ` Riddler [this message]
2024-05-27  1:06       ` Dave Eckhardt
2024-05-28 19:33         ` wb.kloke
2024-05-28 21:49           ` Charles Forsyth
2024-05-29  2:22           ` Dave Eckhardt
2024-05-29  3:32             ` ori
2024-05-29  6:40               ` Steve Simon
2024-05-29  8:29                 ` wb.kloke
2024-05-29  8:17               ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGMcHPofuW1Qhf4-9bAugUDB8B-wvdqgzOrCg4JUf655JSFNDg@mail.gmail.com \
    --to=riddler876@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).