compaction
Compaction（压缩/整理）是计算机科学中的一种数据或内存管理技术，指将分散、碎片化的数据或存储空间重新整合排列，以提高空间利用率和访问效率。该技术广泛应用于内存管理、数据库存储引擎、文件系统及垃圾回收机制中，通过消除碎片化来优化系统性能。在上下文窗口管理场景中，也指对长序列信息进行压缩摘要以支持超长任务处理。
Core Facts
Timeline (last 90 days)
To evaluate whether compression is beneficial or whether switching to a smaller model makes sense, one cannot look only at the drop in Token count per request, but must fix the source input and success criteria while comparing the final task result with the total usage of the entire task (including additional work such as summary generation).
Common methods for controlling the cost of long tasks are caching and compaction, where the former reuses already-processed context and the latter streamlines the history.
The compaction mechanism frees up context space by summarizing and compressing conversation history, but it is essentially a lossy operation that discards a large amount of detail that might otherwise have been useful.
Compaction refers to the framework automatically condensing earlier conversations into summaries or removing redundant content to free up space when session messages exceed the model's context window limit.
Conversation history auto-compaction summarizes earlier conversation history and retains only key context, thereby reducing the token cost of each request and alleviating context window limitations.
Sub-agents have had automatic compaction enabled to improve context management in long sessions.
Automatic compaction frees up context space by summarizing or trimming historical messages, which can reduce the cost of API calls billed per token.
Zed v1.22.0 officially enabled automatic compaction for sub-agents to control context bloat in long-running tasks.
Compaction is a technique in which, when a thread accumulates to a certain length, the system distills the conversation history into a more compact summary rather than simply truncating it.
递归摘要策略对已有摘要再次摘要，形成金字塔式信息压缩层次，在信息密度和计算成本间取得不同平衡点
All Facts (10)
Compaction is a technique in which, when a thread accumulates to a certain length, the system distills the conversation history into a more compact summary rather than simply truncating it.
65%UnverifiedTo evaluate whether compression is beneficial or whether switching to a smaller model makes sense, one cannot look only at the drop in Token count per request, but must fix the source input and success criteria while comparing the final task result with the total usage of the entire task (including additional work such as summary generation).
50%UnverifiedCommon methods for controlling the cost of long tasks are caching and compaction, where the former reuses already-processed context and the latter streamlines the history.
50%UnverifiedThe compaction mechanism frees up context space by summarizing and compressing conversation history, but it is essentially a lossy operation that discards a large amount of detail that might otherwise have been useful.
50%UnverifiedCompaction refers to the framework automatically condensing earlier conversations into summaries or removing redundant content to free up space when session messages exceed the model's context window limit.
50%UnverifiedConversation history auto-compaction summarizes earlier conversation history and retains only key context, thereby reducing the token cost of each request and alleviating context window limitations.
50%UnverifiedSub-agents have had automatic compaction enabled to improve context management in long sessions.
50%UnverifiedAutomatic compaction frees up context space by summarizing or trimming historical messages, which can reduce the cost of API calls billed per token.
50%UnverifiedZed v1.22.0 officially enabled automatic compaction for sub-agents to control context bloat in long-running tasks.
50%Unverified递归摘要策略对已有摘要再次摘要，形成金字塔式信息压缩层次，在信息密度和计算成本间取得不同平衡点
50%