988 karma · joined January 18, 2011
Then, the weapon trades of weight (plastic), against accuracy (in long fire fights). And if that is the correct trade-off to make is of course debatable and depends on the usage.
Couldn't you get in contact with the EFF and work on a more general, more viral form of AGPL, and treat the current license as more of a stop-gap measure? With those viral licenses it is really important to have only a few, so that they are compatible.
W.r.t. to btrfs they are at least working on a fsck tool, even though it can't repair much yet (what it can repair is e.g. some bitflips caused by bad RAM: https://patchwork.kernel.org/patch/4116411/ ).
And stuff like ext4 or ntfs can get back to a state where one can write to it again in most cases.
Another problem is that many applications don't handle EIO well, i.e. they don't give you an option like "Continue with corrupt data", e.g. if a video file gets damaged it doesn't matter much, it'll just be a few damaged pixels, but the whole video player stops playback because it doesn't handle the IO error.
That said, it should only cause memory allocation deadlocks, not corruptions.
Signing apps with normal (EV) code signing certificates is the best we have for other apps, I think. If you detect malware signed by a a certificate you blacklist that one and foward information to the relevant criminal authorities. If they don't investigate you blacklist the whole country. That last step is probably the most controversial one, but otherwise you still have a malware problem.
Also there are patent notices in the TokuDB files.
So probability of it being in Linux at some point approaches zero. And with the patents they even made the whole technique unviable for any Linux fs (haven't looked at them in detail obviously).
It is possible to call bubbles, especially if they are as large and data is transparently available. It is really hard to tell the moment when it will pop, especially if it is connected with the government like in the soviet union or in China.
If you think it is the sellers fault, review the seller. If you think it's the parcel delivery service's fault send it back with that as reason. That is signal enough.
Maybe it also has a strategic advantage? Now every product has to announce they support B2 whereas nobody has to announce they support Wasabi, because they support any S3 compatible storage such as AWS S3, Google Cloud Storage or Wasabi.
Comparable to the L2ARC would be adding the NVMe as swap and then increasing the mysql buffer cache to 400GB or something (don't know if that would work without issues, though). With zswap that would even have compression.
(Applies to the US.) Sheds a bit of light on the motivations behind your treatment and how to get better treatment.
Firefox is doing a good job about analysing extensions startup performance, but I guess they need to do the same thing for page loads and memory usage. Or integrate the extension functionality into core more.
* Do you have active snapshots (vssadmin list shadows)? Halves random writes to disk in the worst case.
* Do you have USN journaling enabled (fsutil usn queryjournal c:)? Adds extra IO to meta-data operations.
* NTFS/FAT is optimized for fast directory listing speed so modifying files also modifies directory entries. Nothing one can do about that (except being aware of that and designing programs with this in mind).
* Windows doesn't keep as much dirty fs data in fs-cache. I know of no way to change that. One can probably, if one uses a Windows Server OS.
* Is a on-access Virus scanner active? If yes, one cannot compare performance to Linux. It's a massive bottleneck.