fenio

3 ms·

1.
by fenio 6d ago
Thanks, all three are fair points. 1. XFS reflink is enabled and its reflink/CoW-break measurements do run. The dashboard button currently means “native/full-CoW filesystem family”, not “supports reflink”, but that distinction is
2.
by fenio 6d ago
First hybrid tier run: https://bartosz.fenski.pl/modern-fs-benchmark/sas-hdd/hybrid... It is FIRST run... I will probably start tuning it now. And I'm open for suggestions what and how to tune ;)
3.
by fenio 6d ago
Should be fixed. Thanks.
4.
by fenio 6d ago
It's not easy to show so many data and make everyone happy about the way it is presented. In fact I'm aiming more at engineers and trying to provide as much info as it is possible to be clear about methodology and everything aroun
5.
by fenio 6d ago
The new machine - I mentioned in the other thread - has both HDDs and SSDs so tests with mixed topologies are planed.
6.
by fenio 6d ago
I extended info about setup. Should be visible in top part of benchmark.
7.
by fenio 6d ago
I answered in other thread how exactly integrity check looks like and why the name might be misleading. I'm also in the middle of updating descriptions to be more adequate. Thanks for pointing that out. Speaking about standard industry
8.
by fenio 7d ago
The current “Integrity” label is broader than the test actually proves, and I’m changing it to “Corruption probe.” FAIL means that file changed or became unreadable. SURVIVED means only that the file remained readable and hash-identical. It
9.
by fenio 7d ago
For the main linked benchmark there are no dedicated test hypervisors. It's all based on GH runners with all the limitations and quirks that came with it. Real hardware is used in: https://bartosz.fenski.pl/modern-fs-be
10.
by fenio 7d ago
Obviously they could and probably were noisy neighbours. I'm not trying to hide that fact. Initial step for every benchmark is test of underlying device to at least reject completely unlucky cases. Also after almost 600 runs average
11.
by fenio 7d ago
what exactly would you like to improve?
12.
by fenio 7d ago
The author of the benchmark here. I went over some comments and I'll try to tackle them here. I'm pretty clear that GH runner based benchmark is far from perfect due to noisy neighbours etc. Thus every test first is running so cal
13.
by fenio 1mo ago
https://mrshu.github.io/github-statuses/
14.
by fenio 2mo ago
I'm working on my own NAS system based on NixOS and bcachefs. https://github.com/nasty-project/nasty
15.
Kubernetes CSI Driver for TrueNAS Scale(github.com)
1 points by fenio 7mo ago|0 comments
16.
GitHub Action to Setup KubeSolo(github.com)
2 points by fenio 11mo ago|0 comments