mirror of
https://github.com/TabbyML/tabby
synced 2024-11-22 17:41:54 +00:00
38 lines
2.1 KiB
Plaintext
Vendored
38 lines
2.1 KiB
Plaintext
Vendored
---
|
|
authors: [ meng ]
|
|
|
|
tags: [tech design]
|
|
|
|
image: ./leaderboard.png
|
|
|
|
---
|
|
# Introducing the Coding LLM Leaderboard
|
|
|
|
In our previous post on *Cracking the Coding Evaluation*, we shed light on the limitations of relying on HumanEval pass@1 as a code completion benchmark.
|
|
In response, we've launched the [Coding LLMs Leaderboard](http://leaderboard.tabbyml.com), embracing **Next Line Accuracy** as a metric inspired by academic works such as [RepoCoder](https://arxiv.org/abs/2303.12570), [RepoBench](https://arxiv.org/abs/2306.03091), and [CCEval](https://arxiv.org/abs/2310.11248).
|
|
|
|
![Leaderboard](./leaderboard.png)
|
|
|
|
But what exactly is line accuracy? In code completion, model predicts a block of code spanning multiple lines.
|
|
A naive approach would involve comparing the predicted block with the actual code being committed directly.
|
|
While this approach might seem ideal, it is often considered "too sparse" as a revealing metric.
|
|
On the other hand, next-line accuracy serves as a dependable proxy for overall block match accuracy.
|
|
|
|
![Next Line Accuracy](./next-line-accuracy.png)
|
|
|
|
<p style={{"text-align": "center"}}>
|
|
|
|
*Only content inside red box are used to compared with ground truth to compute accuracy metric*
|
|
|
|
</p>
|
|
|
|
CCEval utilizes the next statement, but based on our observations, it strongly correlates with next line exact match. Therefore, we've opted for next line accuracy due to its ease of implementation across languages, eliminating the need for language-specific Tree Sitter parsers.
|
|
|
|
For data preparation, our initial release exclusively leverages the dataset from CCEval. This dataset provides well-structured left context, right context, cross-file context with BM25, and oracle information.
|
|
|
|
At present, evaluation is limited to prefix text + cross-file context. Our future plans involve more in-depth analyses:
|
|
|
|
1. Comparing accuracy in completing a function's argument list.
|
|
2. Computing accuracy in completing a function's docstring.
|
|
|
|
We genuinely believe that this leaderboard can assist Tabby's users in navigating the tradeoff between service cost, quality, and other factors. We are committed to enhancing and refining this leaderboard in the future. |