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

use counters to track cache-hit-rate in MapsideReduce #670

Open
johnynek opened this Issue Oct 24, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@johnynek
Collaborator

johnynek commented Oct 24, 2013

useful for tuning the size

@johnynek

This comment has been minimized.

Show comment
Hide comment
@johnynek

johnynek Apr 27, 2015

Collaborator

dup/related to: #1069 #1068

Collaborator

johnynek commented Apr 27, 2015

dup/related to: #1069 #1068

@oeddyo

This comment has been minimized.

Show comment
Hide comment
@oeddyo

oeddyo May 15, 2015

Contributor

So I imagine this is to let Scalding developers run a couple of jobs and see what's a more sensible value to pick for the cache size?

Contributor

oeddyo commented May 15, 2015

So I imagine this is to let Scalding developers run a couple of jobs and see what's a more sensible value to pick for the cache size?

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