google-deepmind / google-deepmind/dm_control

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

Aperta
#425 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
4.7k
Fork
764
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

[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.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.