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

Training too slow problem #13

Open
mamimaka opened this issue May 7, 2023 · 1 comment
Open

Training too slow problem #13

mamimaka opened this issue May 7, 2023 · 1 comment

Comments

@mamimaka
Copy link

mamimaka commented May 7, 2023

Hello @huy-ha , thank you for your open-source and giving such clear guidance.

@mamimaka
Copy link
Author

mamimaka commented May 7, 2023

But when I try to train a decentralized multi-arm motion planner from scratch in our lab's server computer with

mkdir runs
python main.py --config configs/default.json --tasks_path tasks/ --expert_waypoints expert/ --num_processes 16 --name multiarm_motion_planner

I found that I could only use two threads to train, no matter how I changed the parameter 'num_processes'. And this situation made me have to wait for about 700s to accomplish a training step.

To solve this problem, I try to read the codes and have two results.
First, if I added the initialization code of CPU's number in the function initialize_ray(), which is defined in the utils.py, my cpu can be used more. But the training times of every step are not be short.
Second, I set num_processes in the script utils's function setup directly, also no help.

How can I fully use my CPUs to train this motion planner, this problem has troubled me for 3 weeks, I need your help.

@mamimaka mamimaka changed the title Training to slow problem Training too slow problem May 7, 2023
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

1 participant