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

--pool automatically set to 1 in combination with --preread_images #33

Closed
bforsbe opened this issue Jun 29, 2016 · 2 comments
Closed

--pool automatically set to 1 in combination with --preread_images #33

bforsbe opened this issue Jun 29, 2016 · 2 comments

Comments

@bforsbe
Copy link
Contributor

bforsbe commented Jun 29, 2016

Originally reported by: Dimitry Tegunov (Bitbucket: DTegunov, GitHub: DTegunov)


No matter what I set in the GUI, when I press 'print command', it sets --pool 1 if --preread_images is set. I understand that --pool is meant to reduce the number of disk accesses, and that aspect becomes irrelevant when all images are already in memory. However, doesn't it also provide better load balancing within each MPI process? I'm getting better performance if I set it to 30, despite --preread_images. Maybe the default shouldn't be 1?


@bforsbe
Copy link
Contributor Author

bforsbe commented Jun 29, 2016

Original comment by Bjoern Forsberg (Bitbucket: bforsbe, GitHub: bforsbe):


You are correct that load-balancing is improved with increased --pool, but between threads. MPI-load balancing is essentially irrelevant for RELION. If one rank were to entirely halt, all other keep going until all particle images are done. This is why MPI-ranks are in general better to use, but they have a drastic memory-penalty and increased overhead in other aspects, which makes it useful to use a single rank and many threads on each GPU. To load-balance this, --pool is key, yes.

@bforsbe
Copy link
Contributor Author

bforsbe commented Jul 1, 2016

Original comment by Sjors Scheres (Bitbucket: scheres, GitHub: scheres):


I've fixed this in 2.0.b5. Thanks for the report, very useful.

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