Reduce some GC pressure that adds up in several unity workloads. #633
Loading…
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We already have one of those: it's used on line 99:
Empty<T>.Array.We just need to address the tidbit and that's good to go. Thanks for the contribution!
Is this necessary? The new Collection will be using
Empty<TypeReference>.Arrayas it starts empty which is already allocated, and it will grow to4, the default capacity, when needed.oops, fixed.
you're right, reverted.
Thanks again!
@lucasmeijer do you have any indicative numbers on the perf improvements this results in?
@SimonCropp no, the workload I was testing on has high varience, but on many dottrace traces Collection.Grow did show up, and the two causes were the sequencepoints and the generic instantiation arguments. This is definitely in the small fish category.
@lucasmeijer thanks for the clarification