3 ms·
I don't think the CPU overhead is that significant. The memory storage overhead is significant, but that's "solved" by just requiring more memory. I guess we ca
by gridlockd 6y ago
I don't think the CPU overhead is that significant. The memory storage overhead is significant, but that's "solved" by just requiring more memory. I guess we can all thank Java for keeping the DRAM business in good shape.
I'm not talking about what's optimal or efficient, I'm talking about what's evidently "good enough" in the real world.
- fauigerzigerk 6y agoAll GC overheads obviously depend a lot of the specific workload, but if I'm provisioning for a varied workload I would assume 20% CPU overhead and 100% extra memory. Whether or not that's good enough depends on the task as well as on your margins, business model and competition. The cost of hosting grows roughly in proportion with memory capacity (Yes I know it's more complex and nuanced than that). If you deploy on user provisioned hardware (such as on mobile devices or existing/aging PCs), using half as much memory and significantly less CPU/battery than your competitors may give you a competitive edge.