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

Adds method to read the pooling types from model's files #9506

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

flaviabeo
Copy link
Contributor

@flaviabeo flaviabeo commented Oct 18, 2024

This adds a method to load the pooling config file from sentence transformer models like sentence-transformers/all-MiniLM-L12-v2.

The pooling types added can be found at the sentence-transformers Pooling

FIX #9388 (link existing issues this PR will resolve)

cc: @maxdebayser

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE


PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

  • [Bugfix] for bug fixes.
  • [CI/Build] for build or continuous integration improvements.
  • [Doc] for documentation fixes and improvements.
  • [Model] for adding a new model or improving an existing model. Model name should appear in the title.
  • [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
  • [Kernel] for changes affecting CUDA kernels or other compute kernels.
  • [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
  • [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
  • [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

  • We adhere to Google Python style guide and Google C++ style guide.
  • Pass all linter checks. Please use format.sh to format your code.
  • The code need to be well-documented to ensure future contributors can easily understand the code.
  • Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
  • Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels

Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

  • Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
  • Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
  • Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops. See tests/kernels for examples.
  • When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
  • If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

  • After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
  • After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
  • After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
  • Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Copy link

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@robertgshaw2-neuralmagic
Copy link
Collaborator

Thanks! This is great! Can you make sure to add some integration tests?

vllm/model_executor/models/bert.py Outdated Show resolved Hide resolved
MEAN = 3


class PoolingConfig():
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe make this a dataclass?

Comment on lines 260 to 263
def get_pooling_config(model, revision='main'):
"""
This function gets the pooling and normalize
config from the model.
Copy link
Member

@DarkLight1337 DarkLight1337 Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we rename this so it's more obvious that this only applies to sentence-transformers models? We currently have embedding models that are not from sentence-transformers, so it's rather confusing why only BERT accepts PoolingConfig.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry about the force push!! I made a rebase with main to solve the conflicts.

dtype=torch.half if QUANTIZATION == "gptq" else "auto",
max_model_len=MAX_MODEL_LEN) as model:
output = model.encode("Write a short story about a robot that"
" dreams for the first time.\n")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we need to add a verification to make sure that the pooling layer is configured correctly

model_config.max_model_len,
load_config.download_dir,
load_config.load_format,
"mm_processor_kwargs=%s, pooling_config=%s)", VLLM_VERSION,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the linter did more than it should have here. Ideally a commit should not change code lines that are unrelated.

Comment on lines 266 to 280
model_config.rope_scaling,
model_config.rope_theta,
model_config.tokenizer_revision,
model_config.trust_remote_code,
model_config.dtype,
model_config.max_model_len,
load_config.download_dir,
load_config.load_format,
"mm_processor_kwargs=%s, "
"pooling_config_type=%s, normalize=%s)", VLLM_VERSION,
model_config.model, speculative_config, model_config.tokenizer,
model_config.skip_tokenizer_init, model_config.tokenizer_mode,
model_config.revision, model_config.override_neuron_config,
model_config.rope_scaling, model_config.rope_theta,
model_config.tokenizer_revision, model_config.trust_remote_code,
model_config.dtype, model_config.max_model_len,
load_config.download_dir, load_config.load_format,
parallel_config.tensor_parallel_size,
parallel_config.pipeline_parallel_size,
parallel_config.disable_custom_all_reduce,
model_config.quantization,
model_config.enforce_eager,
cache_config.cache_dtype,
model_config.quantization_param_path,
device_config.device,
decoding_config,
observability_config,
model_config.seed,
model_config.served_model_name,
model_config.quantization, model_config.enforce_eager,
cache_config.cache_dtype, model_config.quantization_param_path,
device_config.device, decoding_config, observability_config,
model_config.seed, model_config.served_model_name,
scheduler_config.num_scheduler_steps,
scheduler_config.chunked_prefill_enabled,
scheduler_config.multi_step_stream_outputs,
cache_config.enable_prefix_caching,
model_config.use_async_output_proc,
use_cached_outputs,
model_config.mm_processor_kwargs,
)
model_config.use_async_output_proc, use_cached_outputs,
model_config.mm_processor_kwargs,
model_config.pooling_config.pooling_type,
model_config.pooling_config.normalize)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep this at one argument per line.

Comment on lines 180 to 192
return build_model(model_class,
model_config.hf_config,
cache_config=cache_config,
quant_config=_get_quantization_config(
model_config, load_config),
lora_config=lora_config,
multimodal_config=model_config.multimodal_config,
scheduler_config=scheduler_config,
pooling_config=model_config.pooling_config)
Copy link
Member

@DarkLight1337 DarkLight1337 Oct 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the old indentation is easier to read.

vllm/config.py Outdated Show resolved Hide resolved
vllm/transformers_utils/tokenizer_group/__init__.py Outdated Show resolved Hide resolved
vllm/config.py Outdated
@@ -1835,6 +1851,9 @@ def _get_and_verify_max_len(
raise ValueError(
f"{msg} To allow overriding this maximum, set "
"the env var VLLM_ALLOW_LONG_MAX_MODEL_LEN=1")

if bert_config:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put this at line 1821 like this?

if bert_config and "max_seq_lenght" in bert_config:
    derived_max_model_len = bert_config["max_seq_length"]

Otherwise it will disable the user override logic.

vllm/config.py Outdated
Comment on lines 179 to 180
self.bert_config = self._get_bert_config()
self.do_lower_case = self._get_bert_tokenization_config()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
self.bert_config = self._get_bert_config()
self.do_lower_case = self._get_bert_tokenization_config()
self.bert_config, self.do_lower_case = self._get_bert_config()

vllm/config.py Outdated Show resolved Hide resolved
- dict: A dictionary containing the configuration parameters
for the Sentence Transformer BERT model.
"""
bert_dict = get_hf_file_to_dict("sentence_bert_config.json", model,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! Will be adding these.

return None


def get_sentence_transformer_bert_config(model, revision='main'):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe rename to get_sentence_transformer_tokenizer_config

Comment on lines 28 to 32
if model_config.do_lower_case is not None:
init_kwargs["do_lower_case"] = model_config.do_lower_case

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if model_config.do_lower_case is not None:
init_kwargs["do_lower_case"] = model_config.do_lower_case
if model_config.bert_config is not None and "do_lower_case" in model_config.bert_config:
init_kwargs["do_lower_case"] = model_config.bert_config["do_lower_case"]

Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Copy link

mergify bot commented Oct 29, 2024

This pull request has merge conflicts that must be resolved before it can be
merged. @flaviabeo please rebase it. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Oct 29, 2024
@DarkLight1337
Copy link
Member

DarkLight1337 commented Oct 30, 2024

Sorry, can you hold this for a bit? I'm trying to get #9697 merged which will definitely introduce merge conflicts. The CI is failing on main branch right now so we are all waiting for force merge.

Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Copy link

mergify bot commented Oct 30, 2024

This pull request has merge conflicts that must be resolved before it can be
merged. @flaviabeo please rebase it. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Oct 30, 2024
flaviabeo added a commit to flaviabeo/vllm that referenced this pull request Oct 31, 2024
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
@maxdebayser
Copy link
Contributor

In vllm/engine/arg_utils.py the MEAN type is missing in the set of acceptable values for the command line arg:

        parser.add_argument(
            '--pooling-type',
            choices=['LAST', 'ALL', 'CLS', 'STEP'],
            default=None,

In before the rebase you had a version where this list was generated automatically from the Enum type. Can you add this again?

vllm/config.py Outdated
@@ -107,6 +108,8 @@ class ModelConfig:
can not be gathered from the vllm arguments.
config_format: The config format which shall be loaded.
Defaults to 'auto' which defaults to 'hf'.
bert_config: tokenizationconfiguration dictionary for a given
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bert_config is not actually a parameter of the __init__ method. The documentation can be moved close to the initialization of self.bert_config or removed. Otherwise the docstring will be wrong.

Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
vllm/config.py Outdated Show resolved Hide resolved
Signed-off-by: Flavia Beo <flavia.beo@ibm.com>
Copy link
Contributor

@maxdebayser maxdebayser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: Support sentence-transformers configuration files
4 participants