clab / clab/dynet

non-deterministic behavior on the GPU?

Open
#399 7 comments 0 reactions 0 assignees View on GitHub
good first issue minor bug
Dominant language
C++
Stars
3.4k
Forks
701
PR merge metrics
No merged PRs in 30d

Description

I am unsure why, but we observe some non-deterministic behavior when running on the GPU.
The dynet-seed is set (as well as the python seed and the numpy seed), yet the losses in different runs start to diverge after a while (by the 100th update, is almost surely happens).

This does not happen with the same code on the CPU. Maybe there is a race condition somewhere?

See the following gist:
https://gist.github.com/yoavg/510154a959e76370627a81da173cec9b

`python not_deterministic.py > t1`
`python not_deterministic.py > t2`
`diff t1 t1`

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.