Gemini 3.6 Flash and 3.5 Flash-Lite Ignore Temperature, Top-P, and Top-K
Google's Gemini 3.6 Flash and Gemini 3.5 Flash-Lite ignore temperature, top_p, and top_k, according to Google's current migration guide. Existing Gemini requests…
DeepSeek recently shared some notable financial figures: they could generate about $562K in daily revenue while spending only $87K on infrastructure costs, representing a potential 545% profit margin on their AI inference services. Following my previous article on DeepSeek and GPU export controls, I'm examining how their infrastructure decisions contribute to this potential profitability.
DeepSeek provided detailed operational data in their inference system overview, which reveals some interesting financial metrics:
It's important to understand that "theoretical revenue" here represents what DeepSeek would earn if they charged their full R1 pricing for all tokens processed during the reporting period. This is not their actual revenue, but rather a calculation of what they could potentially earn if all traffic was billed at their premium rate.
For context, if DeepSeek did achieve these figures, they would be earning $5.45 for every dollar spent on infrastructure—well above the 20-30% margins typical in many tech businesses.
DeepSeek's approach to infrastructure optimization is based on several technical strategies:
These technical optimizations directly affect financial performance. By maximizing the efficiency of their GPU resources, DeepSeek can process more tokens per dollar of infrastructure cost compared to less optimized systems.
A notable aspect of DeepSeek's system is their 56.3% cache hit rate – meaning over half of all input tokens are served from their on-disk KV cache rather than being processed from scratch.
This is financially significant because of their differential pricing model. According to their R1 pricing structure, cached tokens cost $0.14/M while new tokens cost $0.55/M. This creates a substantial cost advantage for DeepSeek, as cached tokens require less computational resources while still generating revenue.
The cache system effectively allows DeepSeek to reuse previous computational work, creating a multiplier effect on their infrastructure investment. Each time a token is retrieved from cache rather than recomputed, the system becomes more cost-efficient.
DeepSeek clearly states that their actual revenue is "substantially lower" than the theoretical $562K daily figure for several reasons:
These factors create a significant gap between the theoretical revenue calculation and actual business performance. However, even with these reductions, their technical infrastructure appears capable of supporting a profitable operation with favorable economics compared to industry averages.
The company is essentially operating with a mixed business model that includes both premium paid services and free access points, likely as part of a longer-term growth strategy.
DeepSeek's approach offers several insights for the broader AI industry:
As the AI industry matures, competitive advantage may increasingly come from operational efficiency rather than just model capabilities. DeepSeek's detailed disclosure provides a rare glimpse into the economics of large language model deployment at scale.
While theoretical revenue doesn't equate to actual business performance, the underlying infrastructure efficiencies DeepSeek has achieved appear to create the foundation for potentially sustainable economics in AI service delivery.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com