Perplexity › Perplexity vs Downstream Performance

Perplexity measures how well a model predicts text, but this doesn't always translate to better performance on downstream tasks. The relationship between perplexity and task-specific metrics depends heavily on whether the task fundamentally involves text prediction.

This disconnect became especially apparent in the modern era of large language models. Researchers found that GPT-3, despite having dramatically lower perplexity than GPT-2, didn't always show proportional improvements on specific tasks like mathematical reasoning, code generation, or factual question answering. The model had become better at predicting text in a statistical sense, but text prediction and task performance are not the same thing.

Perplexity tends to correlate well with tasks that directly involve predicting or generating text:

• Speech recognition: Lower perplexity language models produce better transcriptions because ASR systems use language models to score hypotheses, and a better language model makes better predictions about which word sequences are plausible.
• Machine translation: Language model perplexity correlates with translation fluency because a fluent translation is one that sounds like natural text in the target language, exactly what a low-perplexity model captures.
• Text generation: Lower perplexity models generate more coherent text overall, though there can be tradeoffs between coherence and diversity.

For other tasks, perplexity is a poor predictor of performance. The fundamental reason is that these tasks require something beyond next-word prediction:

• Sentiment analysis: A model might have excellent perplexity on movie reviews but poor sentiment predictions. Knowing that "not particularly great" is likely to be followed by "but" doesn't tell you whether the review is positive or negative overall.
• Question answering: Predicting the next word well doesn't mean understanding the content of a passage. A model could achieve low perplexity on Wikipedia text while failing completely at answering factual questions about that same text.
• Named entity recognition: Local word prediction doesn't capture entity boundaries or types. Knowing that "New" is likely followed by "York" doesn't tell you that "New York" is a location entity.
• Reasoning tasks: Multi-step logical or mathematical reasoning requires holding information across many steps, a capability that goes far beyond predicting the next token given recent context.

This limitation motivated the development of benchmark suites like GLUE, SuperGLUE, BIG-Bench, and MMLU that evaluate language models on many downstream tasks simultaneously. These benchmarks provide a more complete picture of model capabilities than perplexity alone. However, perplexity remains valuable as a fast, cheap, unsupervised metric for comparing models during development, precisely because it doesn't require labeled data or task-specific evaluation.