Skip to content
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

Closed
benaadams opened this issue Sep 29, 2017 · 6 comments
Closed
Assignees
Labels
area-System.Collections backlog-cleanup-candidate An inactive issue that has been marked for automated closure. tenet-performance Performance related issue
Milestone

Comments

@benaadams
Copy link
Member

@karelz could you assign this to me?

@AArnott
Copy link
Contributor

AArnott commented Sep 29, 2017

Be sure to test the perf fixes. We've made 'enhancements' to the pooling before that ended up making things worse.

@benaadams
Copy link
Member Author

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?

@AArnott
Copy link
Contributor

AArnott commented Sep 29, 2017

That's a good question for @stephentoub. But I think most corefx perf fixes eventually get back-ported to netfx.

@stephentoub
Copy link
Member

I think most corefx perf fixes eventually get back-ported to netfx.

cc: @AlexGhiondea

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 23, 2020
@layomia layomia removed the untriaged New issue has not been triaged by the area owner label Jun 24, 2020
@ghost
Copy link

ghost commented Oct 26, 2021

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.

@ghost
Copy link

ghost commented Nov 9, 2021

This issue will now be closed since it had been marked no recent activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@ghost ghost closed this as completed Nov 9, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2021
@eiriktsarpalis eiriktsarpalis added the backlog-cleanup-candidate An inactive issue that has been marked for automated closure. label Feb 18, 2022
@ghost ghost removed the no-recent-activity label Feb 18, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Collections backlog-cleanup-candidate An inactive issue that has been marked for automated closure. tenet-performance Performance related issue
Projects
None yet
Development

No branches or pull requests

7 participants