[docs] quant_kwargs#11712
Conversation
sayakpaul
left a comment
There was a problem hiding this comment.
Thanks! Do we have to include an explicit point on how users can derive qaunt_kwargs for a given backend?
There was a problem hiding this comment.
I'm undecided as to what is best, to include each quantization backend here as @sayakpaul mentioned or to an index of them like you did, so I'll leave it to you.
Also I wanted to see the final docs but the doc builder failed.
|
I think it's probably best to refer the user to the specific API docs for each backend where they can find all the relevant arguments, and keep this one more high-level. Not sure why the doc-builder is failing though. bitsandbytes should already be installed in the CI test environment no? 🤔 |
Yeah indeed. I was asking for an explicit note that says just that. |
No actually. I opened #11728 for this. Let's see. |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
| - for granular quantization control, define a `quant_mapping` that provides the quantization configuration for individual model components | ||
|
|
||
| ### Simple quantization | ||
| ### Basic quantization |
There was a problem hiding this comment.
in line 94 there's a link to 'simple quantization' so this will break it, change the other link then?
Improves where you can find the
quant_kwargsin thePipelineQuantizationConfigdocs