Productionize TensorBoard #92
Comments
These classes are similar to EventFileLoader but have functionality for tracking the current offset and size of a record file. This will allow the loader to display a really cool looking progress bar. RecordReader provides a higher level and more Pythonic alternative to PyRecordReader when it comes to reading TensorFlow record files. BufferedRecordReader layers a thread on top of RecordReader and implements the same interface. This will become the default because it doesn't have any impact on local throughput, but is guaranteed to go fast for remote file systems. In the future, we may decouple these classes from PyRecordReader. See tensorflow#92
Introduce RecordReader and BufferedRecordReader These classes are similar to EventFileLoader but have functionality for tracking the current offset and size of a record file. This will allow the loader to display a really cool looking progress bar. RecordReader provides a higher level and more Pythonic alternative to PyRecordReader when it comes to reading TensorFlow record files. BufferedRecordReader layers a thread on top of RecordReader and implements the same interface. This will become the default because it doesn't have any impact on local throughput, but is guaranteed to go fast for remote file systems. In the future, we may decouple these classes from PyRecordReader. See #92
These tables will be used by FileLoader to transactionally import event logs into the database, while maintaining progress. See tensorflow#92
These tables will be used by FileLoader to transactionally import event logs into the database, while maintaining progress. See #92
|
Hi, @jart this issue looks like a vast project, whether there is a design document to describe what you want to make? It is convenient for us to take part in. |
|
@jart How will non Tensor summaries be stored in the database? Will they be converted into Tensors and stored in the Tensors table? |
|
Any news on this? Can you expose a Roadmap related to TB versions? |
|
Still working on getting some functionality off the ground. I plan to communicate as this happens. |
|
Experiment listing, comparison, and search are awesome features. |
|
I'm closing this issue out because a lot of the things we listed earlier are too ambitious and potentially overlap with the work other folks are doing. We'll need to think more about how we want to approach this topic delicately, in a way that dovetails with the efforts of other teams and companies. |
|
Hi @jart , would you please share some stories about what other teams are doing on this topic? Maybe the community can work out a pluggable interface for multi-tenant usages. |
|
Do you plan to add security (password login for instance) to TensorBoard? |
@alexattia an alternative solution consists in using TensorBoard behind a web server and adding an authentication on the web server. |
Note: This information is somewhat of date. New information will be shared shortly.
We have just begun working on making TensorBoard capable of running as a multitenant production service. This issue will be tracking progress and commits relating to this effort.
Prerequisites
Features
Database Support
Cache Support
Productionization
Monitoring
Security
Please note that the list above contains both things: a) we intend to write; and b) would be nice to write. We may not necessarily have time to implement all of the above. If any of these checkboxes are of particular importance to you, or you'd like to see some added, or would like to contribute to their development, then please let us know.
The text was updated successfully, but these errors were encountered: