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

Asynchronous validation #138

Open
jindrahelcl opened this issue Nov 10, 2016 · 1 comment
Open

Asynchronous validation #138

jindrahelcl opened this issue Nov 10, 2016 · 1 comment

Comments

@jindrahelcl
Copy link
Member

Inspired by Nematus, the validation could be done asynchronously.

Do you think it's a good idea?
How do you think this should be implemented?
Are there any non-backward-compatible aspects? (I don't think there are, not sure though)

@jlibovicky
Copy link
Contributor

Generally, I think it is a good idea, but I am not sure how to implement it properly.

Maybe we can have a session that is entirely on CPU, and a separate thread will load the current variables and do the validation. We can also do the validation continuously, regardless on the exact number of the training data - just start a new validation when the previous one has ended. Is it possible in TF?

In any case, I would wait with it until I merge the workflow_refactor branch (and untli the other never-ending branches are merged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants