If you can reduce reference cycles, you will have less of these asynchronous GC runs happening. So we had someone specifically came to me with a whole lot of use cases where he showed when you run this little code, like all these GCs would happen. And we went in there and got rid of a lot of cycles. We actually have a test suite in test slash a a profiling test man usage called cycle test. It's asserting that there's only five GC calls and not 20. Right. But the mean, you're not freeing any, but the, and you're not ref count freeing any either, but you're, you're allocating 700 more. Yeah. I think that