-
Notifications
You must be signed in to change notification settings - Fork 5
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
Use large cluster for slippage execution #321
base: main
Are you sure you want to change the base?
Conversation
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.
Left a discussion comment. Other than that, LGTM.
self, | ||
query: Query, | ||
job_id: Optional[str] = None, | ||
performance: str = "medium", |
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.
In my opinion since this is business critical we should be defaulting to large
. What do you think?
performance: str = "medium", | |
performance: str = "large", |
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.
Yes I like it. In that case we can set the default performance when instantiating the client. I'll move the parameter to the appropriate place.
This makes execution faster and less likely to queue.