diff options
| author |  A. Unique TensorFlower <gardener@tensorflow.org> | 2018-06-27 09:15:47 -0700 |
|---|---|---|
| committer |  Gunhan Gulsoy <gunan@google.com> | 2018-06-28 21:37:43 -0700 |
| commit | 1df29abc5565a9c4a4c67bc69e2bafa80fc7ce9f (patch) | |
| tree | 01cef65e26e575433ed14151af19e8420ea651ba /third_party | |
| parent | 3cc77d4b2217384d6ed7c72c28bdb9552e5e08f4 (diff) | |
[TF2XLA] Don't wrap single-output computations in a tuple and don't resolve constants
Two small-but-not-micro-optimizations:
1) If a computation only produces one output, elide the tuple table by not wrapping it in a single-element tuple.
2) Don't resolve constants at compile time. If we resolve constants, the constant values are not available on the device and this forces us to materialize them, which involves a H2D transfer so is slow. Instead, get the device to materialize them because this is cheap even if they are not used.
PiperOrigin-RevId: 202319850
Diffstat (limited to 'third_party')
0 files changed, 0 insertions, 0 deletions