Skip to content

Clarify post training quantization behaviour #2778

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

Merged
merged 10 commits into from
Mar 11, 2024
2 changes: 1 addition & 1 deletion recipes_source/quantization.rst
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The full documentation of the `quantize_dynamic` API call is `here <https://pyto
3. Post Training Static Quantization
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This method converts both the weights and the activations to 8-bit integers beforehand so there won't be on-the-fly conversion on the activations during the inference, as the dynamic quantization does, hence improving the performance significantly.
This method converts both the weights and the activations to 8-bit integers beforehand so there wont be on-the-fly conversion on the activations during the inference, as the dynamic quantization does. While post-training static quantization can significantly enhance inference speed and reduce model size, this method may degrade the original model's accuracy more compared to post training dynamic quantization.

To apply static quantization on a model, run the following code:

Expand Down