google-deepmind / google-deepmind/dm_control

dm-control mujoco tasks use A LOT of cpu's

Ouverte
#425 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
4.7k
Forks
764
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

[Potentially related to this post](https://github.com/google-deepmind/mujoco/issues/203). 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.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.