feat: add FP16 auto-precision and batching parameters to Reranker #813#817
Open
suhaniiz wants to merge 2 commits into
Open
feat: add FP16 auto-precision and batching parameters to Reranker #813#817suhaniiz wants to merge 2 commits into
suhaniiz wants to merge 2 commits into
Conversation
|
@suhaniiz is attempting to deploy a commit to the param20h's projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
Author
|
@param20h , kindly review this PR which is under GSSoC 2026 |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📋 PR Checklist
🔗 Related Issue
Closes #813
📝 What does this PR do?
This PR introduces performance and memory optimizations to the
Rerankerclass (app/reranker.py):CrossEncodermodel initializer withtorch_dtype=torch.float16. This reduces GPU memory overhead and accelerates inference.batch_sizeparameter (defaulting to 32) to thererank()signature and forwards it directly to the underlyingmodel.predict()function. This prevents CUDA Out-Of-Memory (OOM) exceptions when ranking a massive volume of document chunks simultaneously.🗂️ Type of Change
🧪 How was this tested?
uvicorn app.main:app --reload)npm run devinsidefrontend/)📸 Screenshots (if UI change)
The
torchdependency was safely imported dynamically inside_load_model()to minimize runtime impact if the file is imported elsewhere in environments missing PyTorch. No other core systems are impacted by these optimizations.✅ Self-Review Checklist
dev, notmainmainbranch or any HuggingFace deployment config