-
Notifications
You must be signed in to change notification settings - Fork 668
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
dm-control mujoco tasks use A LOT of cpu's #425
Comments
closing for now -- seems to be something strange happening where CPU's get maxed only in certain circumstances. |
hey david! |
@LiuZhenxian123 sadly I did not solve it. unless you really need DMC, you could try the OpenAI mujoco tasks. if it is happening to you too, I can reopen. |
dm-control seems to try to use all my available CPUs,guess something is wrong with my setting. |
Potentially related to this post. I was wondering why my code slows down when running a few seeds at a time. When I looked, the CPU's are being throttled by running multiple instances of the MuJoCo environments (specifically I was checking with walker-walk). Using just one environment was maxing out several cores. Is there a way to stop this? I compared with hopper/half-cheetah from the Gymnasium implementations and they use just a single CPU per environment. Do I need to change some setting in dm-control to fix this?
If any more information is needed (e.g. resource usage from the terminal), then please let me know what else I can add.
The text was updated successfully, but these errors were encountered: