We can know how much storage each DO used using grapqhl if im not wrong. I did that on my Grafana to knows how much each user is using. Anyway, for the memory footprint, my user case is two: during de dev phase: knows how much i can fit before i need to make another logic to split; For production: I have a DO that does a full text search, and each one downloads (from KV) several documents to make a index... The document size is variable, so i need to download only a small number of files to make sure that i will never blow up the memory, but is not really, really 100% sure.