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

Fix router bugs on max_new_tokens and dataprep gaudi yaml file #273

Merged
merged 5 commits into from
Aug 7, 2024

Conversation

zhlsunshine
Copy link
Collaborator

Description

Fix router bugs on max_new_tokens and dataprep gaudi yaml file. And remove ^M from dataprep xeon yaml file.
This max_new_tokens bug was found when doing performance test by @leslieluyu

Issues

#272

Type of change

List the type of change like below. Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds new functionality)
  • Breaking change (fix or feature that would break existing design and interface)

Dependencies

n/a.

Tests

Set max_new_tokens=17
image

Set max_new_tokens=50
image
image

}
// Merge init request into respReq
for key, value := range initReqData[Parameters].(map[string]interface{}) {
/*if _, exists := respReqData[key]; !exists {
Copy link
Collaborator

Choose a reason for hiding this comment

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

remove this if not needed

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hi @KfreeZ, just let's keep it there, because let's see if they need to keep the response instead overwriting by initial request.

@@ -198,6 +199,32 @@ func executeStep(
return callService(step, serviceURL, input, headers)
}

func mergeRequests(respReq []byte, initReqData map[string]interface{}) []byte {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just curious, why the handleEnsemblePipeline does not need this mergeRequest?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hi @KfreeZ, based on current implementation, EnsemblePipeline have no response case, so just let it there.

@irisdingbj irisdingbj merged commit 5735dd3 into opea-project:main Aug 7, 2024
7 checks passed
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.

3 participants