diff options
| author |  A. Unique TensorFlower <gardener@tensorflow.org> | 2017-03-23 11:10:58 -0800 |
|---|---|---|
| committer | TensorFlower Gardener <gardener@tensorflow.org> | 2017-03-23 12:26:39 -0700 |
| commit | afbeb7df73bc5929644dc33754493122a57da5aa (patch) | |
| tree | eb4b61c7ceb5abd3f133d81ae2dc14e8761462d8 | |
| parent | a1b96fcf0f91e5bea162dc376362a476b077cd85 (diff) | |
Fix typo referring to provided strategy function byte_size_load_fn.
Change: 151036671
| -rw-r--r-- | tensorflow/contrib/training/python/training/device_setter.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tensorflow/contrib/training/python/training/device_setter.py b/tensorflow/contrib/training/python/training/device_setter.py index 53f6fa5436..91b55239bc 100644 --- a/tensorflow/contrib/training/python/training/device_setter.py +++ b/tensorflow/contrib/training/python/training/device_setter.py @@ -35,7 +35,7 @@ class GreedyLoadBalancingStrategy(object): ps ops (typically variables) are created, as it greedily places ops on the least-loaded ps at the point each op is processed. - One reasonable heuristic is the `variable_size_load_fn`, which + One reasonable heuristic is the `byte_size_load_fn`, which estimates load as the number of bytes that would be used to store and transmit the entire variable. More advanced load functions could consider the difference in access patterns across ops, or trade |