-
Notifications
You must be signed in to change notification settings - Fork 193
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
Merge releases/2024/3 into master #720
Merge releases/2024/3 into master #720
Conversation
Workaround Python_VERSION_MAJOR and MINOR not being set by replasing Python3 with Python Disable generation of some of the COMPONENTs not needed for GenAI. There are still unwanted empty archives, but they are generated uncounditionally by rapidjson.
…envinotoolkit#604) That allows LLMPipeline to create ContinuousBatchingPipeline as a backend. There's also a constructor accepting ireq, which can be used if the model was already transformed appropriately for ContinuousBatchingPipeline. But it feels it's going to be misleading and it simpler just to throw if such constructor is called with ContinuousBatchingPipeline backend.
Updated default configurations based on results from CVS-143530. (cherry picked from commit f460002)
Remove unwanted archives
Co-authored-by: Yaroslav Tarkan <[email protected]>
…#642) OpenVINOGenAITargets.cmake was excluded from packaging because CPACK_COMPONENTS_ALL is custom now and doesn't install Unspecified component
Co-authored-by: Pavel Esir <[email protected]>
…oop for greedy sampling (openvinotoolkit#607) Searching for max element in a custom loop gives better performance than using std::max_element
Cherry picked from master
@Wovchena, retarget to OV 24.3 release branch
- Added Readme for python tests - Added `--model_ids` option to run selectively only on specific models --------- Co-authored-by: Zlobin Vladimir <[email protected]>
Symbols that cause errors: - `\u0643` - `\u25aa`
… optional plugin_config in tokenizer (openvinotoolkit#669) This improves performance of CB lib when tested within OVMS. Already merged to master: openvinotoolkit#651 This is cherry-pick
…oolkit#670) [mixtral-8x7b-instruct-v0.1-int4-ov](https://huggingface.co/OpenVINO/mixtral-8x7b-instruct-v0.1-int4-ov/) didn't have `generation_config.json` therefore generation continued ininitely. EOS_TOKEN_ID was red correctly but during generation it was not met. Updated docs so in every generate call max_new_tokens is set either in arguments or via default generation config `pipe.set_generation_config({'max_new_tokens': 100, 'num_beam_groups': 3, ...)` tickets: CVS-146933 CVS-146324
Co-authored-by: Anastasiia Pnevskaia <[email protected]>
Docstring for generation time metrics Ticket: CVS-132859
Co-authored-by: Zlobin Vladimir <[email protected]>
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.
do we have CI runs for these new samples? I don't see it
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.
No. It was last hour merge
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.
do we have a task for it?
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.
Created 148650
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.
Are they applicable only for Stateful pipeline or works will for static / CB as well?
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.
Only for Stateful. I suspect uninitialized perf metrics are returned for CB backend.
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.
Let's create a task for it.
We need unified response for all backends.
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.
Created 148651
@@ -16,7 +16,7 @@ struct SchedulerConfig { | |||
std::size_t num_kv_blocks = 0; | |||
|
|||
// total size of KV cache in GB | |||
std::size_t cache_size = 0; | |||
std::size_t cache_size = 1; |
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.
why? it's explicitly set to 0, so users have to set some meaningful values on their own
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.
It's now possible to construct the struct with all the default values which is used to create CB backend in LLMPipeline.
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.
ok, let's fix it together with CB device name via passing scheduler config as device property
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.
@olpipi, please, address it
- Microsoft Visual Studio 2019 or higher, version 16.3 or later | ||
- Python 3.8 or higher | ||
- Git for Windows | ||
#### Option 2 - setting environment variables manually: |
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.
why do we need to recommend such approach? setupvars is default and we don't need to expose variables manually (which is implementation detail), because we will have to support it in future in case of any changes in OpenVINO scripts.
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.
Developers tend to stop at build step and skip installation part. @TolyaTalamanov is an example.
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.
it's a developer problems that they cannot read readme step by step
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.
They can. But they aren't explained that it's not recommended to skip it and why.
No description provided.