Skip to content
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.

Fixing the reload_frequency to reload_interval and changed default #1

Merged
merged 1 commit into from
Aug 7, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
FROM gcr.io/tensorflow/tensorflow:latest
FROM gcr.io/tensorflow/tensorflow:1.2.1

# Install gsutil
WORKDIR /var/gcloud
Expand Down
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,13 @@ Setup assumes you have [installed the Google Cloud SDK](https://cloud.google.com
3. Write an `app.yaml` file with `runtime: custom` to configure your application. Full reference [here](https://cloud.google.com/appengine/docs/flexible/custom-runtimes/configuring-your-app-with-app-yaml). In the `env_variables` section you must specify 3 environment variables:
* `GCS_PROXY_CONFIG` The fully qualified path to the configuration file you uploaded in step 2.
* `EVENT_FILE_PATH` The fully qualified GCS Path for your Tensorboard summary files.
* `RELOAD_FREQUENCY` Frequency (in seconds) to poll GCS for new summary files.
* `RELOAD_INTERVAL` Frequency (in seconds) to poll GCS for new summary files.

Note that reloading data directly from GCS might cause a lot of API requests and incur high costs, so do not use the strategy
of directly reading from GCS if you use it for more than a few hundreds of log files. This is due to inefficient way GCS direct
access is working currently as described in https://github.com/tensorflow/tensorboard/issues/158

For more frequent reloads/bigger number of log files, syncing the GCS data to local folder using gsutil rsync and loading the data from local folder seems to be a better strategy.

4. Deploy your GAE app.
```
Expand Down
2 changes: 1 addition & 1 deletion example-app.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,5 +8,5 @@ automatic_scaling:
max_num_instances: 1
env_variables:
EVENT_FILE_PATH: gs://ml-workshop/output/mnist_hptuning10
RELOAD_INTERVAL: 1
RELOAD_INTERVAL: 600
GCS_PROXY_CONFIG: gs://ml-workshop/oauth2_proxy.cfg
2 changes: 1 addition & 1 deletion run_tensorboard.sh
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,4 @@
gsutil cp $GCS_PROXY_CONFIG /etc/oauth2_proxy.cfg
export OAUTH2_PROXY_COOKIE_SECRET=`python -c 'import os,base64; print base64.b64encode(os.urandom(16))'`
oauth2_proxy -http-address="0.0.0.0:8080" -upstream="http://127.0.0.1:8081" -config=/etc/oauth2_proxy.cfg 2>&1 &
tensorboard --logdir $EVENT_FILE_PATH --reload_frequency $RELOAD_FREQUENCY --debug --port 8081 --host 127.0.0.1
tensorboard --logdir $EVENT_FILE_PATH --reload_interval $RELOAD_INTERVAL --debug --port 8081 --host 127.0.0.1