-
Notifications
You must be signed in to change notification settings - Fork 0
[Feat] Support LHD #38
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
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 @haochengxia, 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!
I've introduced support for the LHD (Least Hit Density) cache algorithm. This enhancement integrates LHD into our cache simulation framework, making it available for use and testing alongside existing algorithms.
Highlights
- LHD Cache Algorithm Implementation: I've added the LHD class and its initialization function (LHD_init) to libcachesim/cache.py, providing the core logic for the Least Hit Density cache.
- Python API Exposure: The new LHD cache algorithm is now exposed through the main libcachesim package by updating libcachesim/init.py, allowing users to import and utilize it directly.
- C++ Binding Adjustments for LHD: I've modified the find method in src/export_cache.cpp to specifically handle the LHD algorithm's behavior, returning a dummy object for cache hits to ensure proper Python binding interaction.
- Comprehensive Test Integration: The LHD algorithm has been integrated into the existing test suite (tests/test_cache.py), ensuring its basic functionality, eviction, and find methods are covered, with a specific skip for test_basic_get_and_insert due to LHD's unique insert behavior.
- Build System Streamlining: I've removed the scripts/smart_build.py script and updated scripts/install.sh to use pip3, simplifying the build process.
- Dependency Management Refinement: The uv.lock file has been updated to reflect the new libcachesim version and to remove previously included lightgbm and xgboost dependencies, streamlining the project's dependency graph.
- Subproject Update: The src/libCacheSim subproject has been updated to its latest commit, likely incorporating the underlying C++ LHD implementation.
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 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 or fill out our survey 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.
Pull Request Overview
This PR adds support for the LHD (Least Hit Density) cache algorithm to the libcachesim library. The implementation includes a new cache class with appropriate initialization parameters and comprehensive test coverage.
- Add LHD cache algorithm implementation with initialization function
- Integrate LHD into existing test suites with special handling for its unique behavior
- Update submodule reference and build infrastructure
Reviewed Changes
Copilot reviewed 7 out of 9 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
libcachesim/init.py | Exports the new LHD class in the public API |
libcachesim/cache.py | Implements the LHD cache class with standard initialization parameters |
tests/test_cache.py | Adds LHD to all parameterized test suites with special skip logic for insert behavior |
src/export_cache.cpp | Adds special handling for LHD's unique find method return behavior |
src/libCacheSim | Updates submodule commit reference |
scripts/install.sh | Minor change from pip to pip3 command |
scripts/smart_build.py | Complete file removal |
Comments suppressed due to low confidence (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.
Code Review
This pull request adds support for the LHD cache algorithm, including the Python class wrapper and test cases. The changes are generally good, but I've identified a few issues. There's an incorrect command in the installation script that will cause it to fail. More critically, in the C++ bindings, there's a memory management mismatch that could lead to undefined behavior, and a magic number is used which is detrimental to maintainability. I've provided detailed comments and suggestions for these points.
LHD