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.

Sign up for GitHub

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

Jump to bottom

Using CasPool's #10

Open
CollinM opened this issue Oct 25, 2013 · 0 comments
Open

Using CasPool's #10

CollinM opened this issue Oct 25, 2013 · 0 comments
Labels
enhancement

Comments

@CollinM
Copy link
Member

CollinM commented Oct 25, 2013

We need to investigate CAS Pools as a matter of efficiency. It would be a good idea to have a "fixed" upper-bound on the number of CAS's that we keep around. Additionally, we may want to use a similar idea to retain instantiated components, preferably using some smart "most frequently used" metrics.

CasPool Doc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CollinM