-
Notifications
You must be signed in to change notification settings - Fork 35
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
⬆️ TensorFlow 2.9 #724
⬆️ TensorFlow 2.9 #724
Conversation
6dc02ff
to
9e94da6
Compare
Not sure if we should rather set `--incompatible_disallow_resource_jars=false` but this seems to work well. For more info see bazelbuild/bazel#13221
Co-authored-by: Cedric Nugteren <web@cedricnugteren.nl>
I compared the benchmark binaries produced by CI (through bazel, not cmake) from the TF2.8 release with the TF2.9 test-release from this PR. I used a Raspberry Pi 4B at 1.5 GHz with QuickNet from larq-zoo in float. It uses XNNPack for the non-binary layers. For single-threaded benchmarks I found 46.4 ms for both builds, and for 4-threaded benchmarks I found 21.7 ms in both cases. I conclude that the benchmark results did not change with this TF 2.9 upgrade. |
What do these changes do?
This PR updates TensorFlow to version 2.9.0.
How Has This Been Tested?
CI and triggered a test release.
Benchmark Results
TODO