mlsanityData to 14 Oct 2026

COFFE: A Code Efficiency Benchmark for Code Generation

arXiv 2502.02827 ↗First posted 5 Feb 2025cs.SEcited by 20

Not on the map. Why?

Abstract (arXiv)

Code generation has largely improved development efficiency in the era of large language models (LLMs). With the ability to follow instructions, current LLMs can be prompted to generate code solutions given detailed descriptions in natural language. Many research efforts are being devoted to improving the correctness of LLM-generated code, and many benchmarks are proposed to evaluate the correctness comprehensively. Despite the focus on correctness, the time efficiency of LLM-generated code solutions is under-explored. Current correctness benchmarks are not suitable for time efficiency evaluation since their test cases cannot well distinguish the time efficiency of different code solutions. Besides, the current execution time measurement is not stable and comprehensive, threatening the validity of the time efficiency evaluation. To address the challenges in the time efficiency evaluation of code generation, we propose COFFE, a code generation benchmark for evaluating the time efficiency of LLM-generated code solutions. COFFE contains 398 and 358 problems for function-level and file-level code generation, respectively. To improve the distinguishability, we design a novel stressful test case generation approach with contracts and two new formats of test cases to improve the accuracy of generation. For the time evaluation metric, we propose efficienct@k based on CPU instruction count to ensure a stable and solid comparison between different solutions. We evaluate 14 popular LLMs on COFFE and identify four findings. Based on the findings, we draw some implications for LLM researchers and software practitioners to facilitate future research and usage of LLMs in code generation.

Key facts. Cited by 20 papers in the map (data through 14 Oct 2026). First posted on arXiv 5 Feb 2025.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2025: 6; 2026: 14.

20 papers.

Sort:

By area:

  1. 2025HardTests: Synthesizing High-Quality Test Cases for LLM Codingcited by 23
  2. 2025From Code Foundation Models to Agents and Applications: A Comprehensive Survey and Practical Guide to Code Intelligencecited by 15
  3. 2025Scoring Verifiers: Evaluating Synthetic Verification for Code and Reasoningcited by 9
  4. 2026EffiSkill: Agent Skill Based Automated Code Efficiency Optimizationcited by 9
  5. 2026FormulaCode: Evaluating Agentic Optimization on Large Codebasescited by 6
  6. 2025Benchmarking AI Models in Software Engineering: A Review, Search Tool, and Unified Approach for Elevating Benchmark Qualitycited by 4
  7. 2026Towards Secure Logging: Characterizing and Benchmarking Logging Code Security Issues with LLMscited by 2
  8. 2026PerfCodeBench: Benchmarking LLMs for System-Level High-Performance Code Optimizationcited by 2
  9. 2026Evaluating LLMs on Real-World Software Performance Optimizationcited by 2
  10. 2025Learning to Align Human Code Preferencescited by 1
  11. 2026X-Coder: Advancing Competitive Programming with Synthetic Tasks, Solutions, and Testscited by 1
  12. 2026Bridging Generation and Training: A Systematic Review of Quality Issues in LLMs for Codecited by 1
8 more
  1. 2026Cross-Lingual Token Arbitrage: Optimizing Code Agent Context Windows via Local LLM Preprocessingcited by 1
  2. 2026Are Performance-Optimization Benchmarks Reliably Measuring Coding Agents?cited by 1
  3. 2026SWE-NFI: Studying and Benchmarking Coding Agents for Non-Functional Improvementscited by 1
  4. 2025Do AI Models Dream of Faster Code? An Empirical Study on LLM-Proposed Performance Improvements in Real-World Softwarecited by 0
  5. 2026Rethinking Code Performance Benchmarks for LLMscited by 0
  6. 2026Reinforcement Learning for Code Optimizationcited by 0
  7. 2026RLPF: Reinforcement Learning from Performance Feedback for Code Generationcited by 0
  8. 2026Not All Correct Fixes Run Alike: An Empirical Study of Patch Performance in Repository-Level Issue Resolutioncited by 0