3 ms·
To summarise: - your application is using close to 100% available RAM - you don't care about the impact of all those extra writes clogging up CPU caches and b
by rwmj 4y ago
To summarise:
- your application is using close to 100% available RAM
- you don't care about the impact of all those extra writes clogging up CPU caches and bouncing cache lines back and forth across internal buses
- you can't afford to pay for a small amount of extra RAM
In that case reference counting sounds ideal. Good luck!
- zarzavat 4y agoThis was exactly Apple's reasoning for using refcounting in Swift. Although, as I understand it they worked around problem (2) by building their own silicon. If you're on the server then just buy more RAM and use a GC, I agree. But if you're making consumer software then buying more RAM isn't an option. Additionally, RAM costs battery life even when it isn't in use.