-
Notifications
You must be signed in to change notification settings - Fork 286
Fix streaming and threshold #672
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
Conversation
| secret_key: str = "minioadmin", | ||
| bucket_name: str = "a-bucket", | ||
| threshold: int = 10, | ||
| threshold: int = 50, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| threshold: int = 50, | |
| threshold: int = 1000, |
when testing w/ bo20, there are 812 chunks. with stream=True, total runtime goes from 114 to 76s
Seems like the threshold should be higher, which gives a nice perf lift for smaller ingest jobs
edknv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me. I think we can ignore the failing integration test; I don't see how this PR fails the integration test, and it's probably due to some unrelated issues with the build endpoint. However, there is one unit test that is failing and needs updating before merging.
Description
This PR changes how streaming is auto activated. It now checks the count of how many elements (chunks) are processed. The threshold has been increased to 50 given this change. And we also plumbed the stream parameter so you can activate streaming insert to milvus regardless of the number of elements.
Checklist