You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dgriff777 thanks again for providing this amazing repo, was wondering if num_workers should be equal to the number of threads instead of the number of cores as suggested in README.md. I'm new to A3C so please bear with me if this is a naive question :P
The text was updated successfully, but these errors were encountered:
So you don't have the static number of threads on your computer or server that you are using to run this, so number threads would not be a limiting factor here. As this is using python to achieve true parallelism we must use multiprocessing not multithreading as multithreading is the spawning of new threads within in a process and each process for python is run by its own python interpreter and the GIL (global interpreter lock) inhibits true parallel execution of threads within in a process and instead are executed orderly.
The num_workers parameter is just dictating the number of training processes where a model is trained on the game and then shares its updates by updating a shared model between its each process.
@dgriff777 thanks again for providing this amazing repo, was wondering if num_workers should be equal to the number of threads instead of the number of cores as suggested in
README.md
. I'm new to A3C so please bear with me if this is a naive question :PThe text was updated successfully, but these errors were encountered: