Compute Units (CU) represent the computational budget allocated to your research queries, directly influencing the depth and breadth of Caesar’s reasoning process. Each unit roughly corresponds to one minute of processing time and enables additional agentic loops for information gathering, validation, and synthesis.
Compute Units control the number of reasoning steps Caesar performs during research. Think of them as iterative cycles where Caesar:
The computational budget for your research query.
The relationship between compute units and research quality is nuanced. More compute doesn’t always mean better resultsit depends on the nature of your query.
The chart shows Caesar’s performance on Humanity’s Last Exam (HLE), a challenging benchmark of PhD-level questions. Notice the significant jump from 1 to 3 CU (from 19.95% to 53.85%), demonstrating the value of enabling multi-step reasoning.
The dramatic improvement from CU 1 to CU 2-3 occurs because Caesar gains the ability to:
Understanding how Caesar utilizes compute units helps optimize your usage:
Begin with CU 1 (default) and adjust based on response quality. Increase for queries requiring deeper analysis.
Align compute units with query complexity. PhD-level questions benefit from CU 5-7, while straightforward queries work well with CU 1-2.
Each CU adds ~1 minute to processing time. Balance thoroughness with response latency needs.
Beyond CU 5, improvements are often marginal. Reserve higher values for genuinely complex, multi-faceted research.
When you specify compute units in your request:
Caesar internally:
Budget consideration: Your monthly allowance is measured in compute units. Higher CU values consume your budget faster but don’t always yield proportionally better results. Use judiciously.
