Just gave OptiPNG for a spin and sharing my result, just being objective: Test image, 5280z1150z24BPP, saved in irfan PNG Q6: 989KB After OptiPNG, -O5: 900KB webp, lossless: 542KB webp, Q75: 258KB jpq Q75: 491KB (webp Q75 much better image quality)
What fingerprint reader was this?
(But I must admit that arc use almost 1GB memory)
Did try that, only improve slightly...still nothing close to the arc result.
A long forgotten archiver: free-arc produce impressing results. It's not maintained for the last 10 years but still overrun by fare any other compressor this day, at least for data like SQL backup files (.bak) or KVM/QEMU VM .qcow2 files. Example: 512 MB SQL bak file: arc: 26,7MB, 9,17 sec 7z: 36,6MB, 94,00 sec Would love to see 7zip got some of this magic The archives are made using this method, filter and algorithm: "1 rep:96mb+exe+delta+4x4:lzma:96mb:fast:32:mc4" (see attachment) Version 0.67...
https://7-zip.org/a/7z2201-src.tar.xz
Found something here: https://www.7-zip.org/a/7z2201-linux-arm.tar.xz https://www.7-zip.org/a/7z2201-linux-arm64.tar.xz https://www.7-zip.org/a/7z2201-linux-x64.tar.xz https://www.7-zip.org/a/7z2201-linux-x86.tar.xz But the URL's doesn't seem to be published anywhere on sourceforge.net or 7-zip.org :-/
I've found 7z2200-src.tar.xz but it seems to be the source code for Windows. Can I find the source code for the Linux version somewhere?
In relation to https://iperf2.sourceforge.io/IperfCompare.html In my view the one of the biggest differences is that iperf3 doesn't really support Windows. Someone back in 2016 did compile it to Windows (https://iperf.fr), but that's 6 years ago. Secondly iperf3 does support json output!
How the data is organized inside the file doesn't really make any difference, one should still see it as a datafile like any other. One could ask why this is important: If you don't have an understand how the system-design is you might make wrong decision as a user or administrator when doing your setup.
I disagree. I just like any other datafile, just like a word-document. Nothing wrong with that. The problem is you get a wrong idea of the system-design when you call it a database.
As far I can tell the so called database-file is read into memory at start, and then might be saved back by the use in case of changes. If so it's wrong to call it a database, which mean data is read, written and searched continuously, which is not the case. Please consider calling it a "password-file" or the like, so that people doesn't get mislead by a wrong name of what the actual technology in use is.
Wau Linux! That's really good news. Thanks for the effort :-)
Do PeaZip have the source-code for Arc 0.67?
Please close, sorry for the noise (the documentation included in the latest FreeArc version 0.51 is actually for version 0.36, I just noticed, that's why I could find the -ae option).
Please close, sorry for the noise (the documentation included in the latest FreeArv version 0.51 is actually for version 0.36, I just noticed, that's why I could find the -ae option).
Hmm....found something in the documentation of the old version 040: http://freearc.sourceforge.net/FreeArc040-eng.htm
"Unknow" arc options (-ae=aes)
So this only happens when languages is some kind of chinese/asian/non-english?
I love dark themes myself, but there are many other improvments/fixes that should have higher priorities ;-)