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

Choice of headnode instance #13

Open
tomdeakin opened this issue Aug 12, 2020 · 2 comments
Open

Choice of headnode instance #13

tomdeakin opened this issue Aug 12, 2020 · 2 comments

Comments

@tomdeakin
Copy link

How cross platform are the headnode instances? It's often very painful if the mgmt architecture doesn't match the compute node architectures. For instance, on AWS the mgmt node is AMD but we might be launching Arm-based compute nodes. This means I have to compile inside a running job, or deal with installing and using cross-compilers.

@milliams
Copy link
Member

Currently the arch of the head node is fixed to reduce the maintenance burden on us. Our recommendation (and how Chris did it before) is to do the compilation in a running job.

Probably the easiest method is to start an interactive job (for example the srun method here) and do the compilation in there.

Since the head node is usually very small (1 or 2 cores and only a few gigs of RAM) it is not usually suitable for large compilations.

@tomdeakin
Copy link
Author

Makes sense, thanks. Might make a great summer project for someone to add support for this 😄

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

2 participants