In-context learning has established itself as an important learning paradigm for Large Language Models (LLMs). In this paper, we demonstrate that LLMs can learn encoding keys in-context and perform analysis directly on encoded representations. This finding enables lossless prompt compression via dictionary encoding without model fine-tuning: frequently occurring subsequences are replaced with compact meta-tokens, and when provided with the compression dictionary in the system prompt, LLMs correctly interpret these meta-tokens during analysis, producing outputs equivalent to those from uncompressed inputs. We present a compression algorithm that identifies repetitive patterns at multiple length scales, incorporating a token-savings optimization criterion that ensures compression reduces costs by preventing dictionary overhead from exceeding savings. The algorithm achieves compression ratios up to 80% depending on dataset characteristics. To validate that LLM analytical accuracy is preserved under compression, we use decompression as a proxy task with unambiguous ground truth. Evaluation on the LogHub 2.0 benchmark using Claude 3.7 Sonnet demonstrates exact match rates exceeding 0.99 for template-based compression and average Levenshtein similarity scores above 0.91 for algorithmic compression, even at compression ratios of 60%-80%. Additionally, compression ratio explains less than 2% of variance in similarity metrics, indicating that decompression quality depends on dataset characteristics rather than compression intensity. This training-free approach works with API-based LLMs, directly addressing fundamental deployment constraints -- token limits and API costs -- and enabling cost-effective analysis of large-scale repetitive datasets, even as data patterns evolve over time.
Figures & tables
Figure 1: System overview showing hierarchical compression algorithm (right), subsequence finding detail (top left), and compressed output with dictionary (bottom left).
Figure 2: Compression ratios vs. Lmax without dictionary overhead (right) and with dictionary overhead (left). Most datasets show plateau behavior, while some exhibit optimal Lmax values beyond which dictionary overhead reduces compression efficiency.
Figure 3: Template-based decompression results comparing Claude 3.7 Sonnet and Nova Premier across LogHub 2k datasets. Each point represents the average metric score computed over 2,000 logs per dataset.
Dataset
Entries
Templates
Exact Match
Levenshtein
Hamming
Rouge
Apache
51,978
29
0.999
0.999
0.999
0.999
Mac
100,314
626
0.969
0.987
0.975
0.988
Table 1: LogHub Full Dataset Template-Based Results (Claude 3.7 Sonnet)
Figure 4: Compression ratios and decompression quality as a function of Lmax . Top-left: compression ratios by dataset. Remaining panels: Levenshtein, ROUGE, and BLEU scores. Most datasets maintain scores above 0.9 regardless of compression level; outliers (HPC, Thunderbird) show consistently lower scores across all Lmax values, indicating dataset-specific rather than compression-related effects.
Dataset
Levenshtein
ROUGE
BLEU
Apache
0.925±0.048
0.959±0.026
0.918±0.059
BGL
0.928±0.026
0.957±0.014
0.956±0.029
Hadoop
0.945±0.023
0.972±0.010
0.997±0.005
HDFS
0.963±0.042
0.978±0.023
0.978±0.015
HealthApp
0.943±0.028
0.973±0.012
0.956±0.020
HPC
0.823±0.021
0.908±0.012
0.840±0.025
Table 2: Decompression quality for algorithmic compression across Lmax values 3–10. Metrics reported as mean ± std across compression levels. Most datasets (12/14) achieve Levenshtein similarity above 0.90; outliers (HPC, Thunderbird) reflect dataset-specific characteristics discussed in Section 6 .
Figure 5: Relationship between compression ratio and decompression quality. Each point represents one (dataset, Lmax ) configuration. Dashed lines show linear regression fits; shaded regions indicate 95% confidence intervals. R 2 values below 0.02 for all metrics demonstrate that compression intensity does not predict reconstruction quality—performance variation is driven by dataset characteristics rather than compression level.
Dataset
Original Tokens
HPC
13,959
Zookeeper
27,878
BGL
32,951
Apache
36,449
HealthApp
37,533
Spark
39,604
Table 3: Original Token Counts for LogHub-2k Datasets
Claude 3.7 Sonnet
Nova Premier
Dataset
Exact Match
Levenshtein
ROUGE
Exact Match
Levenshtein
ROUGE
Apache
1.000
1.000
1.000
1.000
1.000
1.000
BGL
1.000
1.000
1.000
0.901±0.007
0.958±0.003
0.968±0.003
Hadoop
1.000
1.000
1.000
0.898±0.007
0.959±0.003
0.970±0.003
HDFS
1.000
1.000
1.000
0.949±0.005
0.977±0.002
0.984±0.002
HealthApp
0.996±0.001
1.000
1.000
0.874±0.007
0.920±0.005
0.928±0.005
Table 4: Per-dataset template-based decompression metrics for Claude 3.7 Sonnet and Nova Premier on LogHub-2k (2000 logs per dataset). Per-dataset values reported as mean ± SEM; aggregate row reports mean ± std across datasets.
Appendix figures & tables14 assets
Supplementary material from the paper’s appendix.
Appendix
Figure 6: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Apache dataset and Lmax values.
Figure 7: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for BGL dataset and Lmax values.
Figure 8: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for HDFS dataset and Lmax values.
Figure 9: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for HPC dataset and Lmax values.
Figure 10: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Hadoop dataset and Lmax values.
Figure 11: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for HealthApp dataset and Lmax values.
Figure 12: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Linux dataset and Lmax values.
Figure 13: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Mac dataset and Lmax values.
Figure 14: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for OpenSSH dataset and Lmax values.
Figure 15: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for OpenStack dataset and Lmax values.
Figure 16: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Proxifier dataset and Lmax values.
Figure 17: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Spark dataset and Lmax values.
Figure 18: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Thunderbird dataset and Lmax values.
Figure 19: Levenshtein similarity, ROUGE, and BLEU scores for algorithmic compression for Zookeeper dataset and Lmax values.