-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve performance of Immutable/SecureObjectPool/AllocFreeConcurrentStack #23686
Comments
Be sure to test the perf fixes. We've made 'enhancements' to the pooling before that ended up making things worse. |
Agreed. Question Immutable is OOP'd; there are improvements in corefx that I think it can take advantage of - do I also need to worry about regressions on netfx? |
That's a good question for @stephentoub. But I think most corefx perf fixes eventually get back-ported to netfx. |
cc: @AlexGhiondea |
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process. This process is part of the experimental issue cleanup initiative we are currently trialing in a limited number of areas. Please share any feedback you might have in the linked issue. |
This issue will now be closed since it had been marked |
@karelz could you assign this to me?
The text was updated successfully, but these errors were encountered: