This is assuming that the wide variety of use cases are evenly distributed and that larger use cases are not mostly just a lot of duplicated smaller use cases. If I have a website I will need X amount of ram. If you run a much larger website offering a comparable service you will need some multiple of X, but you don't actually need much more ram per user (assuming you're also accounting for extra infrastructure and not just the web servers). It's the same task just scaled. Relative usefulness is not subjective, you could look at a variety of tasks in different industries. Windows server 2012 had a minimum requirement of 512 MB. Windows server 2025 has a minimum requirement of 2 GB. That's 4x for the same task which totally distorts $/GBs usefulness for being able to tell you anything helpful economically. It's obviously good to collect this data, but you need to pair it with some kind of demand data for it to actually tell you anything.
> you need to pair it with some kind of demand data for it to actually tell you anything.
Again, this is entirely dependant on who is consuming the statistic and for what purpose. For some use cases, yes demand data will be quite crucial. For others it will not. It's quite apparent the site's author doesn't see this as crucial and for the purposes I need to consider memory pricing, I agree.