-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Using tf.estimator.Estimator with save_checkpoint_steps leads to Tensorboard warnings #17272
Comments
I don't think there's enough information here to identify a TF bug. Consider asking another question on Stack Overflow with the |
I am having the same issue, is it possible some workaround or to understand what this is due to? I tried to use all three possible MonitoredSessions (that I know of..) and the result is always the same, that is why I think it is a problem of the CheckpointSaverHook For all the 3 following cases the model is saved, and together with is the graph in a tb event I guess...
A simple code presenting the issue:
|
I have the same issue when using tf.estimator, running the simplest iris code. |
System information
Describe the problem
When using
tf.estimator.train_and_evaluate(...)
with antf.estimator.Estimator
configurated withtf.contrib.learn.RunConfig(save_checkpoints_steps=10, ...)
, aCheckpointSaverHook
will be created automatically. ThisCheckpointSaverHook
will save the graph and graph_def to the summary writer every time it is triggered (see CheckpointSaverHook.before_run).Basic code example:
When starting Tensorboard on the written summary, it will output a hundreds of warnings because of multiple graph defs in the summary which I guess slows it down a lot on startup:
I see there might be issues when using multiple graphs, but for a single graph this seems unpracticable.
Related stack overflow discussion: https://stackoverflow.com/questions/48316888
The text was updated successfully, but these errors were encountered: