WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@ScottLinnn
Copy link
Contributor

Add a flag to config timeout value for this benchmark because the time needed for index covering 100% varies a lot by provider. Hardcoded value fitting one provider will be too large/too small for other provider(s)

@ScottLinnn ScottLinnn requested review from Copilot and removed request for Copilot July 31, 2025 20:23
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a configurable timeout value for the EDW create index benchmark to accommodate varying index building times across different database providers. The change replaces a hardcoded timeout value with a configurable flag.

  • Adds a new command-line flag edw_create_index_benchmark_timeout with a default value of 600 seconds
  • Updates the _MeasureBuildingTime function's default timeout parameter from 120 to 600 seconds
  • Modifies the Run function to pass the configurable timeout value to _MeasureBuildingTime

Comment on lines +58 to +59
'Timeout for the edw_create_index_benchmark in seconds. Default is 600'
' seconds',
Copy link

Copilot AI Jul 31, 2025

Choose a reason for hiding this comment

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

[nitpick] The description should end with a period for consistency with other flag descriptions.

Suggested change
'Timeout for the edw_create_index_benchmark in seconds. Default is 600'
' seconds',
'Timeout for the edw_create_index_benchmark in seconds. Default is 600.'
' seconds.',

Copilot uses AI. Check for mistakes.
@ScottLinnn ScottLinnn requested review from anksena and jnguertin July 31, 2025 20:24
@jnguertin
Copy link
Contributor

Having a flag for the timeout is good, although I recommend setting a default value high enough that all providers that complete in a reasonable time come in under the timeout -- if a provider finishes way before the timeout, that's no problem.

Copy link
Contributor

@jnguertin jnguertin left a comment

Choose a reason for hiding this comment

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

LGTM.

@ScottLinnn ScottLinnn removed the request for review from anksena July 31, 2025 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants