Re:Eager Execution: An imperative, define-by-run interface t...
by make3 on Tuesday October 31, 2017 @04:02PM
(#15596074)
the question now is, are tensorflow eager's RNN as slow as pytorch's are?
[ Parent
| on HN ]
Re:Eager Execution: An imperative, define-by-run interface t...
by yablak on Tuesday October 31, 2017 @07:49PM
(#15597762)
(I'm author of the TF rnn api & tf.contrib.seq2seq)
There's a lot of work being done on this specific part. If you have a standard RNN architecture you want to run, you can probably use the cudnn code in tf.contrib.cudnn to get a super fast implementation.
There is some performance work that needs to be done on properly caching weights between time steps of an RNN if you use a tf.nn.RNNCell. Currently if you want to implement a custom architecture, or a seq2seq decoder, or an RL agent, this is the API you would want to use. Several of the eager benchmarks are based on this API; so that performance will only improve.
I'm hopeful that for the next major release, we'll also have support for eager in tf.contrib.seq2seq.