-
Notifications
You must be signed in to change notification settings - Fork 19.6k
Simulated OpenVINO Backend for Testing Unmerged PR Features with Memory Profiling #21491
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
Conversation
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
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.
Summary of Changes
Hello @Mohamed-Ashraf273, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request is a draft aimed at advancing the OpenVINO backend for Keras by implementing critical operations previously marked as unsupported. The core objective is to enable comprehensive inference capabilities for large language models, specifically demonstrating the functionality of the generate
method for models like GPT2, Gemma, and Mistral. The changes involve complex OpenVINO graph constructions for various array manipulations, slicing, and random number generation, alongside refinements to tensor conversion and general data handling within the backend.
Highlights
- Expanded OpenVINO Backend Capabilities: Implemented several previously unsupported NumPy and core Keras operations, including
slice_update
,repeat
,take_along_axis
,tri
,tril
,triu
, andcategorical
for the OpenVINO backend. This significantly broadens the range of Keras functionalities that can be executed with OpenVINO. - Improved Tensor Handling and Interoperability: Enhanced
get_ov_output
to support list and tuple inputs, enabling more flexible data processing. Additionally,convert_to_tensor
now directly handlesov.Output
objects, andOpenVINOKerasTensor
gained a__array__
method, streamlining conversions and improving interoperability with NumPy. - Enabled Large Language Model (LLM) Inference: The changes enable the
generate
method forGPT2CausalLM
,GemmaCausalLM
, andMistralCausalLM
models on the OpenVINO backend, as confirmed by new test results. This is a crucial step towards full LLM support. - Test Suite Adjustments: Updated
excluded_concrete_tests.txt
to reflect newly supported operations by removing them from the exclusion list. Conversely, certain random operation tests were added to the exclusion list, indicating areas still under development or requiring further integration.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request adds significant new functionality to the OpenVINO backend, including implementations for slice_update
, repeat
, take_along_axis
, tri
, tril
, triu
, and categorical
. This is a great step towards feature parity with other backends. The code is generally well-structured, but some of the new implementations are very complex. I've found a critical bug in the categorical
implementation and have a few suggestions to improve code clarity and maintainability in slice_update
.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #21491 +/- ##
==========================================
+ Coverage 82.81% 82.86% +0.05%
==========================================
Files 565 566 +1
Lines 55520 55963 +443
Branches 8664 8733 +69
==========================================
+ Hits 45977 46376 +399
- Misses 7428 7455 +27
- Partials 2115 2132 +17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ebba7d6
to
b4c38f1
Compare
5482bae
to
208c3d5
Compare
5cd93f9
to
e26fc10
Compare
e26fc10
to
f0ca994
Compare
9c72a94
to
ee5f734
Compare
Device used for inference
CPU
Programming Language
Python
Hardware Architecture
x86 (64 bits)
Model used
GPT-2
Mentions
@rkazants
Performance issue description
During my GSoC project, I've faced this issue:
Running the generate step using OpenVINO backend gives a very high memory usage for some reason, based on these PRs:
Keras_hub: keras-team/keras-hub#2310
OpenVINO performance
for
While TensorFlow shows more memory-efficient usage:
for
Step-by-step reproduction
using these PRs:
Keras_hub: keras-team/keras-hub#2310
run that code: