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

(important) the errors for memory and runs #67

Open
langongjin opened this issue Jul 21, 2019 · 0 comments
Open

(important) the errors for memory and runs #67

langongjin opened this issue Jul 21, 2019 · 0 comments

Comments

@langongjin
Copy link
Contributor

when we run the experiments (e.g., the branch learners) for n_jobs (run in a core). each run in a core will consume a lot of memory. After a lot of testing and meet a lot of weird problems, I finally found the rough consume memory for each run in a core.
It is about 4 Gbits each n_jobs (run in a core). Therefore, generally, do not run more than 16 cores for 64 Gbits memory on ripper1/ ripper2/ripper3.

If you run more cores, you will probably meet the problem like:
image
If you run 16 cores on ripper1/ripper2/ripper3, you will see the perfect ending like:
image
note that 1500 is the terminal iteration.

for more computing platform, we could calculate it with 4 Gbits per cores at least.

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

No branches or pull requests

1 participant