-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[ML] Do not init model memory estimation with the default value #61589
Conversation
Pinging @elastic/ml-ui (:ml) |
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.
Tested locally and LGTM
Verifying test stability in https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/308/ ... |
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.
LGTM
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.
LGTM
: of(DEFAULT_MODEL_MEMORY_LIMIT); | ||
tap(v => { | ||
// eslint-disable-next-line no-console | ||
console.log('New config: ', JSON.stringify(v, null, 2)); |
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.
these log messages are adding a lot of information to the console. are they still needed?
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.
I still need them for checking the flaky test runner, will remove after
retest |
1 similar comment
retest |
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.
Tested latest edits and LGTM
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.
LGTM
It works fine on my local machine. In order to check that this PR doesn't introduce test flakiness, we're validating it in 40 runs here: |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
ML tests passed 40 times in https://kibana-ci.elastic.co/job/kibana+flaky-test-suite-runner/332/, so it seems no test flakiness has been introduced ✔️ |
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.
LGTM
…tic#61589) * [ML] do not init model memory estimator with the default value * [ML] enhance model_memory_estimator logic, update unit tests * [ML] don't call the endpoint when start the job cloning * [ML] unit tests * [ML] use skip * [ML] remove unused parameter * [ML] try to disable 'disable-dev-shm-usage' * [ML] revert webdriver.ts, add debug logging * [ML] add debug logging * [ML] fix time range initialization * [ML] fix with useMemo * [ML] fix categorization validation check * [ML] remove wrong setIsWizardReady * [ML] revert page.tsx, update model_memory_estimator.ts and tests, skip failing tests * [ML] adjust unit test description * [ML] fix _runAdvancedValidation * [ML] support async validation init of categorization job creator * [ML] adjust unit tests
…) (#62430) * [ML] do not init model memory estimator with the default value * [ML] enhance model_memory_estimator logic, update unit tests * [ML] don't call the endpoint when start the job cloning * [ML] unit tests * [ML] use skip * [ML] remove unused parameter * [ML] try to disable 'disable-dev-shm-usage' * [ML] revert webdriver.ts, add debug logging * [ML] add debug logging * [ML] fix time range initialization * [ML] fix with useMemo * [ML] fix categorization validation check * [ML] remove wrong setIsWizardReady * [ML] revert page.tsx, update model_memory_estimator.ts and tests, skip failing tests * [ML] adjust unit test description * [ML] fix _runAdvancedValidation * [ML] support async validation init of categorization job creator * [ML] adjust unit tests
Summary
Follow up on #60888.
Prevent the model memory estimator to emit the default value on subscription start.
Checklist