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
TF 2.x Feature: Flops calculation #552
Comments
There seems to be a new API tf.profiler.experimental.Profile, would this work for you? |
Hi @chenmoneygithub ! |
@mohantym Hi! I will need to follow up the specific team to find more details. To make clear, are you looking for how to calculate flops using |
@chenmoneygithub ! |
@mohantym |
@sidml ! |
If you open a GitHub issue, here is our policy:
It must be a bug, a feature request, or a significant problem with the documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
Here's why we have that policy:.
Keras developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.
System information.
TensorFlow version (you are using):
2.8
Are you willing to contribute it (Yes/No) :
No
Describe the feature and the current behavior/state.
Transferring the issue #32809 from TF Core repo to here as @bhack suggested. Currently we don't have a dedicated api to calculate flops of models or functions. It would be great to have a dedicated api to calculate flops.
Describe the feature clearly here. Be sure to convey here why the requested feature is needed. Any brief description about the use-case would help.
Earlier tf.compat.v1.profiler.profile was being used in 1.x version to calculate flops from graphs of model files. But this approach is not working accurately for 2.x code base . A 2.x api for flops calculation will be very useful for community.
Will this change the current api? How?
No
Who will benefit from this feature?
It will largely benefit those who are looking to calculate floating point operations for their models and methods.
Contributing
The text was updated successfully, but these errors were encountered: