perf: avoid output_hidden_states when only last_hidden_state is used #4755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What does this PR do?
Avoid unnecessary
output_hidden_states=Truewhen only the final layer hidden state is usedto compute reward logits.
Currently, the model enables
output_hidden_states=Truebut only consumeshidden_states[-1]. This forces the backbone to store all intermediate layeractivations, increasing memory usage and compute overhead.
This PR switches to
output.last_hidden_state, which is functionally equivalentto
hidden_states[-1], while keeping the behavior unchanged.Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
Who can review?
Anyone in the community is welcome to review this PR.