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

way to determine optimal MapReduce memory and job number settings #55

Open
vadasg opened this issue Nov 7, 2012 · 0 comments
Open

way to determine optimal MapReduce memory and job number settings #55

vadasg opened this issue Nov 7, 2012 · 0 comments
Assignees

Comments

@vadasg
Copy link
Member

vadasg commented Nov 7, 2012

It would be nice to have a way to detect the size of the biggest vertex in memory, then use this to allocate memory for Map and Reduce jobs (and also set the number of said jobs). It may be possible to do this from Titan albeit slowly and then output a properties file for use with Faunus.

@ghost ghost assigned vadasg Nov 7, 2012
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