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

We need a cache allocator... #35

Closed
GoogleCodeExporter opened this issue Jul 15, 2015 · 1 comment
Closed

We need a cache allocator... #35

GoogleCodeExporter opened this issue Jul 15, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Contributor

Currently we have two cache allocators:
   * connection structures
   * suffix usage

Currently both of them use a shared pool of resources from all threads, and
we might want to make them thread local. We don't need two implementations
of the same functionality, so we should refactor the code.

I have pushed a proposal for a cache allocator (compatible with libumem if
you have that) on github:

http://github.com/trondn/memcached/tree/cache_alloc


Original issue reported on code.google.com by trond.no...@gmail.com on 19 Mar 2009 at 11:05

@GoogleCodeExporter
Copy link
Contributor Author

Fixed and documented in trunk. see 652884e33425aca52be61438482fc0b6f9b5ab08

Original comment by trond.no...@gmail.com on 18 Apr 2009 at 1:21

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant