Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[for Pytorch users] Why should one use TensorboardX if torch.utils.tensorboard is available? #656

Open
taras-sereda opened this issue Jan 31, 2022 · 2 comments

Comments

@taras-sereda
Copy link

Hey guys, great work on developing this repo! It's quite popular and apparently trusted by many people given the number of stars.

I have one important question. Why should one use TensorboardX instead of torch.utils.tensorboard?
I see that TensorboardX is tested with pytorch 1.8.1, but right now pytorch 1.10.1 is already available.

It's clear to me that this repo can be used with other DL frameworks which don't have tensorboard integration. That some code bases are already using TensorboardX. But when it comes to development of a new project in pytorch, would you use TensorboardX? If so then why exactly?

Thanks!

@shouldsee
Copy link

shouldsee commented Sep 1, 2022

Is there a hidden relation between these two modules?

Seems like torch.utils.tensorboard was based on tensorboardX code as indicated by its early commits

@fellhorn
Copy link
Contributor

fellhorn commented Apr 6, 2023

I can tell you one reason, why people are using tensorboardX instead of torch.utils.tensorboard is the direct support for writing the tfevent files to Google Cloud Storage. In torch.utils.tensorboard relies on tensorboard for this feature, which comes with a large storage overhead if your only goal is to write the files to GCS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants