• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle


  • That’s because the drive was written to its limits; the defrag runs a TRIM command that safely releases and resets empty sectors. Random reads and sequential reads /on clean drives that are regularly TRIMmed/ are within random variance of each other.

    Source: ran large scale data collection for a data centre when SSDs were relatively new to the company so focused a lot on it, plus lots of data from various sectors since.






  • And this is happening on the BETA channel. If you're running beta, and you expect no issues, you're an idiot. If you're running beta, and you're unable to investigate those issues and resolve them (Which, as you've such a clear, lucid understanding of what's going on you clearly are able to), then you're an idiot. If you've enabled developer options without understanding tech, and how to fix things yourself, you're an idiot.

    There's no protecting against idiots, they're on their own.

    The vast majority of people will not see this issue because you have to go out of your way to see this bug.






  • I’m going to briefly explain why I downvoted… this (I feel) is an unhelpful comment that doesn’t explain anything. You say, “[if] you’re comfortable support a broken-by-design network, do it.”, but you don’t explain why it’s a broken-by-design network.

    I’ll say - I agree with you, but the comment doesn’t actually enhance the conversation and comes off as abrasive and unhelpful. If I’m looking for information, I’d rather be given education (Even if it’s just a, “Go here for why you don’t do that!”), not just a, “Don’t do it” with no assistance and help for how to do it right.