i can only speak from experience, but i have had fossil and venti running on a
single ssd (on a radpberry pi) for 5 years now - no rotating discs left at home.
i have mtime changes and ephemeral snapshots turned off to reduce the update
rate. i chose a sandisk card, and take backups just in cas
Finally,. SSDs just die over time. Especially if they are
not powered on and refreshing. JEDEC specs say that they
should retain data for 1 year unplugged when stored at 30
degrees celsius, assuming the internet isn't lying to me.
Keep backups.
Quoth Dave Eckhardt :
> > For the napkin calculation
> For the napkin calculation: On disk, the IEntry is 38Bytes. Alas,
> writes occur always in (the ssd internal) blocksize. So, essentially
> (assuming 4096 byte blocksize, which is quite optimistic), we have
> a write efficiency of less than 1 percent.
While I see how such a model can predict di
i'm curious what straightforward storage structure wouldn't be. trying to
second-guess ssd firmware seems a tricky design criterion.
On Tue, 28 May 2024 at 20:34, wrote:
> For the napkin calculation: On disk, the IEntry is 38Bytes. Alas, writes
> occur always in (the ssd internal) blocksize. So,
For the napkin calculation: On disk, the IEntry is 38Bytes. Alas, writes occur
always in (the ssd internal) blocksize. So, essentially (assuming 4096 byte
blocksize, which is quite optimistic), we have a write efficiency of less than
1 percent.
A good firmware in the ssd could avoid needing a n
