From: wb.kloke@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Throwing in the Towel
Date: Wed, 29 May 2024 04:29:46 -0400 [thread overview]
Message-ID: <17169713860.3BE8E9.69061@composer.9fans.topicbox.com> (raw)
In-Reply-To: <5B3282E2-DB89-4C78-8901-B2832E1EBB64@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
> i'm curious what straightforward storage structure wouldn't be. trying to second-guess ssd firmware seems a tricky design criterion.
>
Designing for minimal disk stress: Never rewrite data already written to disk. Now we have big and quite cheap main memory.
I don't critisize the historical design choices. But times have changed.
If I had to design a venti now, I would drop the variable length blocks for 8k blocks (or whatever blocksize a modern fossil would use).
Further, I would store the data directly into disk blocks.. In a parallel log I would store the scores, so that the scores and blocks just can be referenced by the block number.
At start up, read the score file and construct a memory search tree for a suitably shorted part of the score. (See Mechiel Lukkien's memventi).
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2ca67486c7a13a77-M26ca440629fc61a3eeb0bab2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1700 bytes --]
next prev parent reply other threads:[~2024-05-29 8:29 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
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 [this message]
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=17169713860.3BE8E9.69061@composer.9fans.topicbox.com \
--to=wb.kloke@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).