-
Notifications
You must be signed in to change notification settings - Fork 593
Implement LoadGen server_coalesce_queries flag #618
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
Implement LoadGen server_coalesce_queries flag #618
Conversation
|
Unfortunately, the multi-thread IssueQuery() needs to wait until tomorrow.... Still debugging :( |
|
How do I turn this feature on and off by a user? |
|
@christ1ne By default it's off. To turn on, set the |
|
@christ1ne @guschmue @tjablin Is it fine if we merge this first? I think this feature has less concern and it will make #620 look cleaner. Thanks! |
|
fine with me |
|
@tjablin ... good with it? |
|
Test at my local, no obvious performance degradation observed when this patch is applied and whether server_coalesce_queries flag is used or not. |
|
@tjablin Sorry for pinging. I have addressed all your comments. Could we merge this PR? Thanks |
Changes:
sleep_until()if in Server scenario and if the current time has already passed the current query's scheduled time.server_coalesce_queriesflag. When this flag is set to true, LoadGen will issue multiple samples per query when the current time has already passed multiple queries' scheduled timestamps.