REVIEW 2 cited by
Code-Optimise: Self-Generated Preference Data for Correctness and Efficiency
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Code Language Models have been trained to generate accurate solutions, typically with no regard for runtime. On the other hand, previous works that explored execution optimisation have observed corresponding drops in functional correctness. To that end, we introduce Code-Optimise, a framework that incorporates both correctness (passed, failed) and runtime (quick, slow) as learning signals via self-generated preference data. Our framework is both lightweight and robust as it dynamically selects solutions to reduce overfitting while avoiding a reliance on larger models for learning signals. Code-Optimise achieves significant improvements in pass@k while decreasing the competitive baseline runtimes by an additional 6% for in-domain data and up to 3% for out-of-domain data. As a by-product, the average length of the generated solutions is reduced by up to 48% on MBPP and 23% on HumanEval, resulting in faster and cheaper inference. The generated data and codebase is open-sourced at https://github.com/huawei-noah/HEBO/tree/Code_Optimise.
Forward citations
Cited by 2 Pith papers
-
Can We Generate Images with CoT? Let's Verify and Reinforce Image Generation Step by Step
Applying test-time verifiers, DPO preference alignment, and a new adaptive reward model (PARM) to autoregressive image generators improves GenEval score from 53% to 77%.
-
Language Models for Code Optimization: Survey, Challenges and Future Directions
A systematic review of 53 papers on using large language models for code optimization, with a taxonomy, five challenges, and eight future research directions.
Discussion (0). Continue with ORCID to comment.