-
Notifications
You must be signed in to change notification settings - Fork 47
Fix some metrics #339
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
Fix some metrics #339
Conversation
Summary of ChangesHello @hiyuchang, 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 focuses on improving the observability and robustness of the system by introducing comprehensive timing metrics across key components like the Explorer, Trainer, and DataJuicer client. It also refines existing metric handling, standardizes naming conventions, and makes the metric aggregation utility more resilient to edge cases, ultimately providing clearer performance insights and a more stable metric collection process. 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.
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 aims to fix and improve metrics, particularly timing metrics, across the system. The changes include:
- Standardizing metric names for better clarity (e.g.,
time/read_experience). - Adding timing for operations in
DataJuicerClient,Explorer, andTrainer. - Refactoring
gather_metricsto handle empty lists gracefully, which simplifies calling code by removing redundanttry-exceptblocks.
The implementation is mostly solid, especially the robust timing logic in explorer.py and the simplification in gather_metrics. However, I've identified a logical issue in the new timing implementation within trinity/trainer/trainer.py where the metric time/train_total_time does not measure the full duration between syncs as intended. My review includes a detailed comment on how to correct this to ensure the metric is accurate and consistent with other parts of the codebase. Overall, good improvements to observability.
|
/unittest-diff |
Summary
Failed Tests
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-algorithm |
Summary
Failed Tests
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-algorithm |
Summary
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-explorer |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-common |
Summary
Tests
Github Test Reporter by CTRF 💚 |
Description
As the title says.
Checklist
Please check the following items before code is ready to be reviewed.