Skip to content
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

Initializing server with an adapter sets it as the default #370

Merged
merged 7 commits into from
Apr 2, 2024

Conversation

tgaddair
Copy link
Contributor

@tgaddair tgaddair commented Apr 2, 2024

Previously, initializing the LoRAX server with an adapter would merge its weights into the base model and prevent dynamic adapter loading. In practice, this runs counter to the value prop of LoRAX, which is to support many adapters at runtime, and is incompatible with planned extensions like speculative decoding adapters.

This PR changes the behavior so that specifying --adapter-id during init will set that as the default adapter used when no adapter ID is provided for the request. This allows for setting fallback adapters that can be generally useful for most requests when the user does not know which adapter they should use at runtime, and in cases where using something like a strong baseline speculative decoding adapter is a reasonable default for most queries.

@tgaddair tgaddair merged commit 5d2211f into main Apr 2, 2024
2 checks passed
@tgaddair tgaddair deleted the def-adapter branch April 2, 2024 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant