Eh, it’s one of those perpetual rivalry things where the answer will probably never be known, and doesn’t really matter except when it comes to petty squabbles between nations.

Le pavlova etait un plat de nouvelle zealand. Si Bluey connais la, c’est parce que la recette etait vole.

Add accents to your pleasing…

No I don’t.

Many but not all will have a ‘total TBW’ metric, but that is more of a ‘how many write cycles can this theoretically last’ metric. What I am predominantly interested in is “how many TB can be written before sporadic write delays start occurring”

The best way to learn it, is to set yourself a goal/problem, define as best as possible how many unique issues that problem can be broken into, then start solving them one-by-one, periodically stopping to evaluate how they fit together.

Learning the best languages and structures to use will come as result of this.

^^ that person first though.

The thing that is always painfully missing from any benchmark, is an endurance test.

I want to know how many TB I can write consecutively before the disk starts to degrade in performance and stop being useful. So far the only way I have been able to achieve this is to purchase a couple of every disk and stress them until failure, logging that interval, and selecting the winners for usage.

I do not care about how fast it can write over the course of five minutes, I want to know how fast it can write over the course of five hours continuous usage.

This is a very broad question, the answer to which will almost definitely be “yes, but”, so knowing what you are trying to achieve would be helpful.

You don’t. Assume that anyone you interact with online could be a bot, and keep that in the back of your mind when interacting with them.