Re: [9fans] [PATCH] fossil: fix a deadlock in the caching logic

[Charles Forsyth <charles.forsyth@gmail.com>]

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

It was the different characteristics of hard drives, even decent SATA,
compared to SSD and nvme that I had in mind.


On Sat, 8 Apr 2023 at 15:30, Charles Forsyth <charles.forsyth@gmail.com>
wrote:

> zfs is very big, complicated and the code looks ancient. I did not enjoy
> working with it.
>
> On Sat, 8 Apr 2023 at 08:51, hiro <23hiro@gmail.com> wrote:
>
>> fixing another couple deadlocks makes you finally consider ditching
>> fossil?
>> zfs storage isn't always permanent either, for example if you use
>> encryption or deduplication.
>>
>> On 4/6/23, Lucio De Re <lucio.dere@gmail.com> wrote:
>> > On 4/6/23, noam@pixelhero.dev <noam@pixelhero.dev> wrote:
>> >> Quoth Charles Forsyth <charles.forsyth@gmail.com>:
>> >>> fussing about certain things for hard drives that probably don't
>> matter
>> >>> for
>> >>> SSD let alone nvme
>> >>
>> >> I am once again asking you to be more specific, please :)
>> >>
>> >> I have Plans for improving venti for myself, it'd be great to actually
>> >> have a specific list of issues that others have noticed!
>> >>
>> > I presume that fossil doesn't apply special treatment to SSD and NVME
>> > which to my limited understand could be a serious downside. I guess
>> > I'm asking whether one should seriously consider ditching the
>> > fossil/venti combination and consider centralising permanent storage
>> > on something like ZFS instead?
>> >
>> > Lucio.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T354fe702e1e9d5e9-M3a916ec52a7ef1d354e615bd
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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