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

[Bench] Specialize OpenAI endpoint for backends not supporting debug config #2962

Merged
merged 1 commit into from
Oct 5, 2024

Conversation

MasterJH5574
Copy link
Member

This PR specializes the OpenAI endpoint with the option of "not attaching debug_config". Prior to this PR, when --ignore-eos is enabled, a debug_config field is included in the payload for MLC to recognize. However, some backend servers (e.g., vLLM) do not support this debug_config field. So we need to manually specify not attaching this field when benchmarking these backends.

@MasterJH5574 MasterJH5574 force-pushed the 10-05-bench-no-debug-config branch 2 times, most recently from 2d1bb9a to c48aad0 Compare October 5, 2024 06:52
…config

This PR specializes the OpenAI endpoint with the option of "not
attaching `debug_config`". Prior to this PR, when `--ignore-eos` is
enabled, a `debug_config` field is included in the payload for MLC
to recognize. However, some backend servers (e.g., vLLM) do not
support this `debug_config` field. So we need to manually specify
not attaching this field when benchmarking these backends.
@tqchen tqchen merged commit d9b6c98 into mlc-ai:main Oct 5, 2024
2 checks passed
MasterJH5574 added a commit that referenced this pull request Oct 5, 2024
…config (#2962)

This PR specializes the OpenAI endpoint with the option of "not
attaching `debug_config`". Prior to this PR, when `--ignore-eos` is
enabled, a `debug_config` field is included in the payload for MLC
to recognize. However, some backend servers (e.g., vLLM) do not
support this `debug_config` field. So we need to manually specify
not attaching this field when benchmarking these backends.
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.

2 participants