lz4_flex
zfs
| lz4_flex | zfs | |
|---|---|---|
| 13 | 720 | |
| 411 | 10,125 | |
| - | 0.6% | |
| 6.5 | 9.7 | |
| 21 days ago | 7 days ago | |
| Rust | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lz4_flex
-
Hetzner ARM cax11 vs Intel cx11 Benchmark
I run a benchmark based on my LZ4 implementation (de/compressor) between cax11 and cx11 since the instances cost the same. The code doesn't use any SIMD.
-
lz4_flex 0.11: Gainzzzzz Unleashed!: Performance Improvements Detailed in Blogpost (LZ4 De/compression)
By the way, the PR removing bounds checks from extend_from_within_overlapping is up: https://github.com/PSeitz/lz4_flex/pull/141
- lz4_flex (fast LZ4 de/compression) 0.10 released, now with legacy frame support ~ also 1Mio downloads 🎉
-
ZAP: a VERY fast zip alternative, written in rust!
Zap uses LZ4 as it's primary compression algorithm, although I might add ZSTD as an option too. The LZ4 crate i'm using goes over the compression better than I can in the span of a comment. Check it out here.
-
lz4_flex 0.9 released
I wrote something here how hc could work: https://github.com/PSeitz/lz4_flex/issues/21
-
lz4_flex 0.8 released with support for frame format and major performance improvements
Yes, the updated benchmarks are here: https://github.com/pseitz/lz4_flex#results-v080-17-05-2021-safe-decode-and-safe-encode-off
- Lz4_flex – fast LZ4 implementation in Rust
-
LZ4, an Extremely Fast Compression Algorithm
I ported the block format to Rust matching the C implementation in performance and ratio.
https://github.com/pseitz/lz4_flex
-
lz4_flex 0.7.2 reaches parity with cpp reference implementation on speed and ratio
Following this change count_same_bytes is unsound - it offsets the pointer by the value of candidate without any bounds checks, which may result in out-of-bounds access.
- lz4_flex 0.7 supports no_std (thanks @coolreader18), 32bit and is dependency-free
zfs
-
Radxa's SATA HAT makes compact Pi 5 NAS
> The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.
Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(
https://github.com/openzfs/zfs/discussions/14793
- OpenZFS: Fix corruption caused by MMAP flushing problems
- ZFS: Some copied files are still corrupted (chunks replaced by zeros)
-
DiskClick: Ever wanted to hear Old Hard drive sounds
IMO the "next fs" is just zfs. They somewhat recently merged RAIDZ expansion feature https://github.com/openzfs/zfs/pull/12225 and make regular improvements. If no file system has what you need today, zfs will probably be the first one to have it "tomorrow," imo.
- OpenZFS bug reports for native encryption
-
A data corruption bug in OpenZFS?
https://github.com/openzfs/zfs/issues/15526#issuecomment-181...
> zpool get all tank | grep bclone
> kc3000 bcloneused 442M
> kc3000 bclonesaved 1.42G
> kc3000 bcloneratio 4.30x
> My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.
-
Ask HN: What's your "it's not stupid if it works" story?
A couple years ago, I had an idea for convincing a filesystem to go faster using 2 compression steps instead of one. I couldn't see why it wouldn't work, and I also couldn't convince myself it should.
It seems to have worked out. [1]
[1] - https://github.com/openzfs/zfs/commit/f375b23c026aec00cc9527...
-
ZFS Profiling on Arch Linux
https://github.com/openzfs/zfs/issues/7631
This is a long-standing issue with zvols which affects overall system stability, and has no real solution as of yet.
-
Using ZFS on single disks, combining them with mergerfs, and paritizing them with Snapraid
TIL. Thank you! https://github.com/openzfs/zfs/pull/15022
-
Why does primarycache=metadata reduce my un-cached read speeds?
Difference may be significant, yes https://github.com/openzfs/zfs/pull/14243
What are some alternatives?
LZ4 - Extremely Fast Compression algorithm
zstd - Zstandard - Fast real-time compression algorithm
density - Superfast compression library
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
squashfs-tools-ng - A new set of tools and libraries for working with SquashFS images
RocksDB - A library that provides an embeddable, persistent key-value store for fast storage.
snapper - Manage filesystem snapshots and allow undo of system modifications
zstd-rs - zstd-decoder in pure rust
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption