howiec wrote: ↑15 Nov 2020, 19:31
Discord hammers your registry and disk with about 40,000 events per minute.
Origin is generating roughly 22,000 disk read/write events per minute.
Great catch!
Do you have the stats screenshots? And any links to any issue tracking system? (I don't know if they use a public github-style or BugZilla-style system -- but if they do -- then mutliple expert users should pile-in statistics).
Many modern systems have a lot of write caching, write levelling and algorithms that will greatly mitigate thsese writes. So the 40,000 events per minute will likely coalescence to just about 10 to 60 actual SSD writes per minute, likely all on different sectors even for the same block in the same file (thanks to automatic wear leveling algorithms). Windows 10 does a massive amount of coalescencing for registry writes and batches them up, so the actual writes are much more intermittent (like once a second or once every two seconds).
However, with the increase in users using TLC and QLC SSDs which are more wear-sensitive, it becomes a concern when an application hammers an SSD excessively, especially since it can add latency to the user's game to have background disk accesses occuring several hundreds times per second.
Think like a security researcher: How do security researchers urgently reach corporations? They have techniques:
-- In some cases -- given an unlimited budget -- it becomes useful to purchase paid LinkedIn credits ($$$) and actually message a PM or software engineers directly (after searching/finding them down);
-- Or other unconventional reporting techniques such as mailing a FedEx envelope with printouts-proof to that said contact -- like a security researcher might do when they're having difficulty reaching a corporation about a rather severe security hole.
Basically high-priority-contact channels that sometimes require spending money. It's a royal pain, but often quite super very effective if the right contacts are surgically selected (a PM, and a couple of top engineers), to catch a company's attention. This move must be done carefully and surgically, only for the most high-emergency bug reports when all other channels fail. Overloading these channels means they tend to close and the company gets harder to reach. But the trick is often to not exclusive rely on the common Level 1 retail-contacting channels and low-effort contacting channels: Just clicking Send on an email is not enough. Legwork and money is usually needed to catch a balky corporation's attention.
Mind you, thanks to realatively good coalescencing of SSD writes in the modern era -- I don't think this kind of issue (yets) warrants such an unusual escalation so try lower-lying apples like finding Discord channels (like a Discord channel with a bug reporting area) -- but if further data (at the SSD controller level) shows issues -- then carefully selected headlines like "Discord is damaging my SSD: I have a debug log and screenshot") -- sometimes such bait catches attention when a boss or PM does a double take and then asks an engineer if it's real, etc. Use your marketing skillz & school essay paper skillz (correct paper title selection etc) as appropriate.
