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

About the lock in multiprocess of A3C. #20

Open
liuxz-cs opened this issue Mar 3, 2021 · 1 comment
Open

About the lock in multiprocess of A3C. #20

liuxz-cs opened this issue Mar 3, 2021 · 1 comment

Comments

@liuxz-cs
Copy link

liuxz-cs commented Mar 3, 2021

Excuse me, I want to know whether the lock is needed in the multiprocess of A3C. I have saw some codes of the implement of A3C, and sometimes they use a lock when they update the gradient of shared model with the single worker of A3C. So is the usage of the lock necessary?

@jakkarn
Copy link

jakkarn commented May 4, 2021

I would suggest reading the paper included in the Readme: https://arxiv.org/pdf/1602.01783.pdf. They mention the lock-free approach Hogwild! that can make learning more efficient.

It's probably good for some problems, and worse suited for other problems.

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

2 participants