If I manually deduplicate/copy a 1GB file, how many such offset/refcount tuples would be created in RAM? Just one for the whole file, or one per underlying 128kB block?
This is so much better than automatically doing dedup and the RAM overhead that entails.
Doing offline/RAM+in memory dedup size optimizations seem like a really good optimization path. In the spirit of also paying only what you use and not the rest.
Edit: What's the RAM overhead of this? Is it ~64B per 128kB deduped block or what's the magnitude of things?
The only 'supported' WireGuard implementation that exists is written by you in C, yet you complain that my C++ implementation lacks memory safety. Where is the logic?
As the author of TunSafe and µTorrent, I wonder if you base that statement on facts or is it just an attempt at spreading FUD and general dislike against non open-source applications?
I agree, his project is very cool. Kevtris is where I got the inspiration to make my own FPGA NES from. I also mentioned him, and linked to his web page, in my blog post.