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

successful prediction using evaluate.py but terminal hangs for 30 seconds before exiting to command prompt #54

Closed
darienacosta opened this issue Jul 11, 2020 · 3 comments

Comments

@darienacosta
Copy link

darienacosta commented Jul 11, 2020

Hi,

I was successful in using evaluate.py to generate expected output to "predictions-x.txt"
However I noticed that the script doesn't return to command line for another 30 seconds. The last log I see is

error_handling.py:101] prediction_loop marked as finished

And then it's an awkward 30 seconds to wait. Is this normal behavior? Is there anything I can do to eliminate the lag? Is this just the way TF works?

Thanks

@darienacosta darienacosta changed the title successful prediction using evaluate.py but terminal hangs for 30 seconds before exiting successful prediction using evaluate.py but terminal hangs for 30 seconds before exiting to command prompt Jul 11, 2020
@JingqingZ
Copy link
Collaborator

Hi, I think the program may need a few seconds to release resources. Given you have got the expected output, this should be fine.

@darienacosta
Copy link
Author

Thanks. I think you're right. Even if I kill the script midprocess, it still takes some time to return to prompt.

@rohithsiddhartha
Copy link

Hey If I just pass a tf-record with one example with features inputs and targets. Evaluate execution has happened and then after finishing just text_metrics-2-.dev.txt file is created and the prediction and targets and inputs text file hasn't created. So, Ideally I can't view prediction generated by model if I just pass single example in tfrecord.

If I pass tf-record with 9 examples then it's using the whole 60gb ram from the instance and taking longer time for finishing the task.

Would like to explain why this is happening?

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

3 participants