It's a very convoluted variant of Mark and Sweet. It has two generations of objects, young objects and all objects. All objects are Mark and Sweet and young objects are point-to-date on the location. The net effect is that if you're having a lot of small objects that get allocated all the time and forgotten really quickly, allocation takes like on average around one CPU instruction. But then you have pipelining, so sometimes it takes slightly less. Okay. So let's talk about the garbage collector just for a moment. Is it a mark in sweep garbage collector? This episode is brought to you by Code Ship. Maintain centralized control over your organization's projects and teams with