This model is deprecated. We only continue performance benchmarking for the default 10k input token workload. Results for other workloads are historical and no longer updated.

DeepSeek has launched a newer model, DeepSeek-V2.5. We suggest considering it instead.

For more information, see comparison of DeepSeek-V2.5 to other models and API provider benchmarks for DeepSeek-V2.5.

DeepSeek Coder V2 Lite Instruct logo
DeepSeek
•

Open weights model

•

Released June 2024

DeepSeek Coder V2 Lite Instruct API Provider Benchmarking & Analysis

Model Comparison

Analysis of API providers for DeepSeek Coder V2 Lite Instruct across performance metrics including latency (time to first token), output speed (output tokens per second), price and others. API providers benchmarked include .

Fastest

Output speed

Total 0 providers

Lowest Latency

Time to first token

Total 0 providers

Lowest Price

Blended price (per 1M tokens)

Total 0 providers

No API providers are currently available for DeepSeek Coder V2 Lite.

Benchmarks of providers are not available for this model.
Please see the models page for DeepSeek Coder V2 Lite Instruct for details of the model and its intelligence compared to other models.

Highlights

Speed

Output tokens per second · Higher is better
No data available

End-to-End Response Time

Seconds · Lower is better
No data available

Price

USD per 1M tokens (blended) · Lower is better
No data available

Pricing

Pricing: Cache Hit, Input, and Output

Price (USD per M Tokens) · Lower is better · 10,000 input tokens
No data available

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Price per token included in the request/message sent to the API, represented as USD per million Tokens.

The blended cache price shown here uses cache hit price only. Other caching costs differ by provider:

  • Anthropic: charges a separate cache write fee, with different rates for 5-minute and 1-hour TTLs (1-hour TTL is more expensive).
  • Google (Vertex/Gemini): charges a per-hour cache storage fee in addition to cache hit pricing. Some providers also use tiered pricing for prompts above 200K tokens.
  • OpenAI, DeepSeek, others: typically charge only cache hit pricing with no write or storage fee.

See Prompt Caching for the full breakdown.

Price per token generated by the model (received from the API), represented as USD per million Tokens.

Pricing: Blended Price

Blended at 7:2:1 (cache-input-output) · USD per 1M tokens (blended) · Lower is better
No data available

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

The blended cache price shown here uses cache hit price only. Other caching costs differ by provider:

  • Anthropic: charges a separate cache write fee, with different rates for 5-minute and 1-hour TTLs (1-hour TTL is more expensive).
  • Google (Vertex/Gemini): charges a per-hour cache storage fee in addition to cache hit pricing. Some providers also use tiered pricing for prompts above 200K tokens.
  • OpenAI, DeepSeek, others: typically charge only cache hit pricing with no write or storage fee.

See Prompt Caching for the full breakdown.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

Output Speed vs. Price

Blended at 7:2:1 (cache-input-output) · Output speed: output tokens per second · USD per 1M tokens (blended)
Most attractive quadrant
No data available

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

The blended cache price shown here uses cache hit price only. Other caching costs differ by provider:

  • Anthropic: charges a separate cache write fee, with different rates for 5-minute and 1-hour TTLs (1-hour TTL is more expensive).
  • Google (Vertex/Gemini): charges a per-hour cache storage fee in addition to cache hit pricing. Some providers also use tiered pricing for prompts above 200K tokens.
  • OpenAI, DeepSeek, others: typically charge only cache hit pricing with no write or storage fee.

See Prompt Caching for the full breakdown.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

Speed

Measured by Output Speed (tokens per second)

Output Speed: DeepSeek Coder V2 Lite Instruct

Output speed: output tokens per second · 10,000 input tokens
No data available

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Figures represent performance of the model's first-party API (e.g. OpenAI for o1) or the median across providers where a first-party API is not available (e.g. Meta's Llama models).

Latency vs. Output Speed

Latency: seconds to first token received · Output speed: output tokens per second · 10,000 input tokens
Most attractive quadrant
No data available

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Time to first token received, in seconds, after API request sent. For reasoning models which share reasoning tokens, this will be the first reasoning token. For models which do not support streaming, this represents time to receive the completion.

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

Latency

Measured by Time (seconds) to First Token

Time to First Token

Seconds to first token received · Lower is better · 10,000 input tokens
No data available

Time to first token received, in seconds, after API request sent. For reasoning models which share reasoning tokens, this will be the first reasoning token. For models which do not support streaming, this represents time to receive the completion.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

End-to-End Response Time

Seconds to output 500 tokens, calculated based on time to first token, 'thinking' time for reasoning models, and output speed

End-to-End Response Time

Seconds to output 500 tokens, including reasoning model 'thinking' time · Lower is better · 10,000 input tokens
No data available

Seconds to receive a 500 token response. Key components:

  • Input time: Time to receive the first response token
  • Thinking time (only for reasoning models): Time reasoning models spend outputting tokens to reason prior to providing an answer. Amount of tokens based on the average reasoning tokens across a diverse set of 60 prompts (methodology details).
  • Answer time: Time to generate 500 output tokens, based on output speed

For fair comparison, the number of reasoning tokens is standardized across all providers for each model based on the model's representative query token counts.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

Key Comparison Metrics & API Features

No results.

Frequently Asked Questions

Common questions about DeepSeek Coder V2 Lite Instruct providers

DeepSeek Coder V2 Lite Instruct is not currently available through any API providers we benchmark. As an open weights model, it can be self-hosted.