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

Memory limit does not restrict data size properly #7

Closed
kpdecker opened this issue Aug 15, 2014 · 1 comment · Fixed by #10
Closed

Memory limit does not restrict data size properly #7

kpdecker opened this issue Aug 15, 2014 · 1 comment · Fixed by #10
Labels
bug
Milestone

Comments

@kpdecker
Copy link
Contributor

@kpdecker kpdecker commented Aug 15, 2014

Currently running a catbox cache using config of

        "pack": {
                "cache": [
                        {
                                "engine": "catbox-memory",
                                "shared": true
                        }
                ]
        },

Which should default to a 100MB cache limit. Currently seeing instances of this cache in the 389MB range as reported by heapdump while under load. Trying to get more information about the state, but mdb is not cooperating right now.

kpdecker added a commit to kpdecker/catbox-memory that referenced this issue Aug 15, 2014
Previously no tracking was done so the cache size was effectively infinite.

This fixes hapijs#7
@kpdecker

This comment has been minimized.

Copy link
Contributor Author

@kpdecker kpdecker commented Aug 15, 2014

This is fixed by kpdecker@f048264 but that code is dependent on #9.

kpdecker added a commit to kpdecker/catbox-memory that referenced this issue Aug 15, 2014
Previously no tracking was done so the cache size was effectively infinite.

This fixes hapijs#7
@geek geek added the bug label Aug 15, 2014
@geek geek added this to the 1.0.5 milestone Aug 15, 2014
@geek geek closed this in #10 Aug 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.