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 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.
Just did a cursory read of the commits related to security for this release, and my assumpion based solely on the changes, is that it’s not a remote-access vulnerability, but a supply-chain-esque vulnerability where a video you downloaded from a questionable source might trigger code embedded in the metadata to be run by jellyfin.