feat: Incorporated Saha Sourav's feedback - #3
Conversation
Summary of ChangesHello @RianKoja, 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 incorporates feedback by refining the mechanism for forcing lazy evaluation in benchmark operations, specifically for fireducks, to ensure accurate performance measurements. It also expands the benchmarking suite by adding a Highlights
Using Gemini Code AssistThe 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 by creating a comment using either
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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. 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
|
There was a problem hiding this comment.
Code Review
This pull request incorporates feedback by changing the lazy evaluation trigger for fireducks to ._evaluate() and adds a new groupby-first-rank benchmark for fairer comparison. The changes are logical and align with the PR's goal. I've left a few comments with suggestions for improvement, mainly around maintainability. Specifically, I've noted the use of an internal method and pointed out opportunities to reduce code duplication in the new benchmark tests. Overall, these are good changes that improve the benchmark suite.
This changes the method to force lazy evaluation on fireducks from
.result()to._evaluate()as the proper method to avoid unfair computations.The groupby-dense-rank operation has a bug on fireducks that slows it down, but will hopefully be fixed soon. For a fairer comparison, a groupby-first-rank benchmark was also added.