11–20 of 62 posts
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.
Earlier quoted context omitted.
Uhm, what? There are tons of ways to prevent data loss, none of them involves writing the data out to tapes and then back in again.
Sure, you can also write to disk or other media. But are you trying to argue that certain large companies don't use tape?
There's simply no good reason to periodically write your data from flash to $other every now and them, and then back to flash. There are heaps of other ways to prevent data loss or performance degradation in flash storage.
There are methods like tiered storage, where only the most active data is present in Flash-storage, much like write back caching.
Maybe I haven't been paying attention, but I've never had a site attach extra text to copied text like this site does. I wanted to see what the test machine's case looks like, so I copied the make and model and pasted it into a search bar, and got "Read more:" and a link to the page along with the text I wanted to copy. No thanks. I'll be skipping that site in the future, unless that javascript comes from a place I c…
Why on earth are you you blocking javascript using dns? Shouldn't you be doing it via the browser (via addons or site preferences)?
> importantly, for all SSDs, disable write-cache buffer flushing for best performance. Is this actually good advice, especially without mentioning the durability risks?
The biggest players in the game do not use SSDs for persistent storage longer than x weeks. It is offloaded to tape at some point and restored periodically.
What's the endurance of these devices? Could I rely on the swap file for large cfd meshes in a pinch for a week?
It says in the article.
> importantly, for all SSDs, disable write-cache buffer flushing for best performance. Is this actually good advice, especially without mentioning the durability risks?
StackOverflow answer here: https://superuser.com/a/1215634 It's essentially the typical "without this enabled, you will lose data in case of power loss, potentially breaking the O/S".
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.
Earlier quoted context omitted.
StackOverflow answer here: https://superuser.com/a/1215634 It's essentially the typical "without this enabled, you will lose data in case of power loss, potentially breaking the O/S".
Dont most SSDs have capacitors for this?
> importantly, for all SSDs, disable write-cache buffer flushing for best performance. Is this actually good advice, especially without mentioning the durability risks?
The biggest players in the game do not use SSDs for persistent storage longer than x weeks. It is offloaded to tape at some point and restored periodically.
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.
Maybe I haven't been paying attention, but I've never had a site attach extra text to copied text like this site does. I wanted to see what the test machine's case looks like, so I copied the make and model and pasted it into a search bar, and got "Read more:" and a link to the page along with the text I wanted to copy. No thanks. I'll be skipping that site in the future, unless that javascript comes from a place I c…
>unless that javascript comes from a place I can easily block with pi-hole. Why on earth are you you blocking javascript using dns? Shouldn't you be doing it via the browser (via addons or site preferences)?