Is this actually good advice, especially without mentioning the durability risks?
It's essentially the typical "without this enabled, you will lose data in case of power loss, potentially breaking the O/S".
can you elaborate on this? What's the exact difference? Do sata drives get more aggressive buffer flushing than nvme drives?
I bought one that should power my internet+wifi for about an hour for $45.
I guess even a small one like that would handle power blips for a home server, but in an outage the battery would quickly run out and the setting would matter.
I didn't do a lot of research, my main goal was to not have interruptions when the power blinks off.
There's APC and Amazon basics models that are about the same capacity and price.
This makes no sense. The main problem with disabling write flushing is what happens if the OS crashes or the power goes out. Doing periodic backups/restores provides a "last known good state" to revert to, but you'll still lose all the writes between the last backup and when you crashed. Depending on your workload this might be fine, but I doubt the COO is going to be pleased when he finds out you lost all customer orders from today.
The bit about "restoring periodically" also doesn't make any sense because such events are easily detectable. There's no need to constantly take the system offline to do a restore. Disabling write flushing isn't going to cause increased bitrot.
Exactly! Use ceph so you don't have to care about burning ssd/hdd/server/switch/racks/dc, you have your object-storeage, FS, block-device, with one service and that's it.
No thanks. I'll be skipping that site in the future, unless that javascript comes from a place I can easily block with pi-hole.
document.addEventListener('copy', (event)=>{
const pagelink = `\n\nRead more: ${document.location.href}`;
event.clipboardData.setData('text', document.getSelection() + pagelink);
event.preventDefault();
})
To prevent this make a custom extension "run_at": "document_start"
and inject window.addEventListener('copy', e => e.stopImmediatePropagation(), true);
alternatively use for example https://www.tampermonkey.net with Experimental Inject Mode: Instant
to inject your pacifying script.Why on earth are you you blocking javascript using dns? Shouldn't you be doing it via the browser (via addons or site preferences)?
I ended up getting a Samsung Evo 970 plus (1TB) a while ago because it was in a sale for $85. Almost half the speed of the ones in the benchmark. Maybe I should have waited.
And 1/3 the price. If you bought it because it was on sale, doesn't that mean you're at least somewhat price sensitive? I don't think you should feel bad about your purchase.
Even in the latter, full text indexing which every platform has had for years now makes it much less likely that the full directory tree will even get walked, and differences even less likely to be noticed. As a side note, every desktop platform's full text search seems to suffer software performance problems that are largely independent of the underlying disk
Even in the full-tree enumeration case, since Spectre/Meltdown mitigations landed, system call overhead is so high now that even with a lightning fast disk, a large chunk of total time taken to walk the directory tree is lost basically twiddling the CPU mode securely. You can definitely still see the difference between SATA and NVMe, but you can also definitely measure the amount of time during the NVMe run that is spent in software -- incrementally faster NVMe will have quickly diminishing returns.
"What about databases!" This was my original interest in SSDs to begin with. It turns out, despite being a data monkey who loves large databases, since 2013 any time I've worked with a giant dataset like this, it is always in the form of large scans (usually from something like a CSV or XML file), where SSDs don't really have a mind-blowing advantage over magnetic (but of course they are still 5-10x faster a seq io, its just that data parsing and processing is typically the bottleneck now).
It says in the article.
The only time I max out my sata scratch drive is when I’m unpacking a video. Playing a 4K and a 1080p video at the same time barely spikes my ZFS pool on my NAS.