Chinese Language Is Not More Efficient Than English in Vibe Coding: A Preliminary Study on Token Cost and Problem-Solving Rate
Organizations: Tsang · ∗,†Scam.ai
Abstract
A claim has been circulating on social media and practitioner forums that Chinese prompts are more token-efficient than English for LLM coding tasks, potentially reducing costs by up to 40%. This claim has influenced developers to consider switching to Chinese for ``vibe coding'' to save on API costs. In this paper, we conduct a rigorous empirical study using SWE-bench Lite, a benchmark of software engineering tasks, to evaluate whether this claim of Chinese token efficiency holds up to scrutiny. Our results reveal three key findings: First, the efficiency advantage of Chinese is not observed. Second, token cost varies by model architecture in ways that defy simple assumptions: while MiniMax-2.7 shows 1.28x higher token costs for Chinese, GLM-5 actually consumes fewer tokens with Chinese prompts. Third, and most importantly, we found that the success rate when prompting in Chinese is generally lower than in English across all models we tested. We also measure cost efficiency as expected cost per successful task -- jointly accounting for token consumption and task resolution rate. These findings should be interpreted as preliminary evidence rather than a definitive conclusion, given the limited number of models evaluated and the narrow set of benchmarks tested due to resource constraints; they indicate that language effects on token cost are model-dependent, and that practitioners should not expect cost savings or performance gains just by switching their prompt language to Chinese.
Figures & tables
Appendix figures & tables3 assets
Supplementary material from the paper’s appendix.
Appendix
| English Prompt | Chinese Prompt (original characters) |
| TSQL - L031 incorrectly triggers “Avoid using aliases in join condition” when no join present Expected Behaviour Both queries should pass; only difference is the addition of a table alias ‘a’: SELECT [hello] FROM mytable and with alias: SELECT a.[hello] FROM mytable AS a Observed Behaviour 1/ passes 2/ fails with: L031: Avoid using aliases in join condition. No join condition present :-) Steps to Reproduce Lint queries above Dialect: TSQL Version: sqlfluff 0.6.9, Python 3.6.9 | Chinese Prompt Translation |
| Model | Lang | Inst | Res | Rate | Prompt/Inst | Output/Inst | Reason/Inst |
|---|---|---|---|---|---|---|---|
| MiniMax-2.7 | EN | 50 | 33 | 66.0% | 298,720 | 61,762 | 22,368 |
| MiniMax-2.7 | ZH | 39 | 24 | 61.5% | 382,974 | 79,182 | 28,677 |
| GPT-5.4-mini | EN | 50 | 18 | 36.0% | 84,347 | 2,695 | 0 a |
| GPT-5.4-mini | ZH | 46 | 12 | 26.1% | 91,681 | 2,929 | 0 a |
| GLM-5 | EN | 48 | 31 | 64.6% | 1,417,012 | 112,803 | 87,474 |
| GLM-5 | ZH | 49 | 27 | 55.1% | 1,388,094 | 110,501 | 85,688 |
| Tokenizer | ZH/EN Ratio | EN chars/tok | ZH chars/tok |
|---|---|---|---|
| GLM (chatglm3-6b) | 0.923 | 2.69 | 2.16 |
| Qwen (Qwen2-7B) | 1.025 | 3.57 | 2.72 |
| Mistral (Mistral-7B) | 1.064 | 2.78 | 1.96 |
| Llama (cl100k_base) | 1.150 | 3.72 | 2.46 |
| GPT (cl100k_base) | 1.150 | 3.72 | 2.46 |
LLM Inference Efficiency
Large language model inference efficiency reduces the time, memory, energy, and cost of generating useful outputs.
See all 350 papers