-
Notifications
You must be signed in to change notification settings - Fork 197
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
Preload / Prewarm custom models via URL on startup #475
Conversation
Models used for said manual testing:
CLIP
|
Thanks for the testing matrix! Is the no "name" behaviour the same as when creating an index with this model normally? What is the expected behaviour @wanliAlex ? |
Yes, because |
Do we want to hold this PR for a while until my custom HF models are merged? Do we want to test the custom HF models prewarming? |
The name check is here But note that the |
I'm under the impression this URL pre-warming feature is high priority, so it can be merged asap, but I'll need confirmation from @pandu-k If ever, do we see the format for HF/S3 models being much different? Or are they also in the form |
Yeah they are similar. Feel free to merge if it's urgent as this is for production use. |
Let's get this merged in first, so we can spin up a testing tag |
The PR looks good to me. Just to confirm, did you do the manual test on a dockerised marqo? @vicilliar |
Ah good idea, i have not yet. Will do so |
I did the tests on a local running marqo |
Can you try to run several manual tests on a dockerised marqo and upload some screenshots? Would this be enough to test the production environment? @pandu-k |
That should be pretty good. Try expected failure and expected successful cases. Ensure that search/add docs works as expected. The testing matrix was super useful |
return True | ||
assert run() | ||
|
||
# TODO: test bad/no names/URLS in end-to-end tests, as this logic is done in vectorise call | ||
|
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.
can we have one more test to ensure the prewarmed model will not need to be download/load again?
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.
can we have one more test to ensure the prewarmed model will not need to be download/load again?
For both search and add_document.
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.
this we can save for the API end-to-end test
|
failing 1 unit test on local:
|
…into joshua/prewarm-any-model merging remote changes
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
Currently, the env var only accepts strings.
What is the new behavior (if this is a feature change)?
This allows the env var
MARQO_MODELS_TO_PRELOAD
to accept custom models as dicts withmodel
andmodel_properties
. A sample declaration would look like this:Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Have unit tests been run against this PR? (Has there also been any additional testing?)
Manual testing. Application tests will be made once the env var customization feature in Marqo API tests finishes
Related documentation changes (link commit/PR here)
To follow
Please check if the PR fulfills these requirements