Qwen2.5 Coder 32B: API Provider Benchmarking & Analysis
Analysis of API providers for Qwen2.5 Coder 32B Instruct across performance metrics including latency (time to first token), output speed (output tokens per second), price and others. API providers benchmarked include Hyperbolic, Fireworks, and Deepinfra.
Comparison Summary
Output Speed (tokens/s): Fireworks (104 t/s) and Deepinfra (54 t/s) are the fastest providers of Qwen2.5 Coder 32B, followed by & Qwen2.5 Coder 32B, Hyperbolic.Latency (TTFT): Deepinfra (0.25s) and Fireworks (0.32s) have the lowest latency for Qwen2.5 Coder 32B, followed by & Qwen2.5 Coder 32B, Hyperbolic.Blended Price ($/M tokens): Deepinfra ($0.18) and Hyperbolic ($0.20) are the most cost-effective providers for Qwen2.5 Coder 32B, followed by & Qwen2.5 Coder 32B, Fireworks.Input Token Price: Deepinfra ($0.18) and Hyperbolic ($0.20) offer the lowest input token prices for Qwen2.5 Coder 32B, followed by & Qwen2.5 Coder 32B, Fireworks.Output Token Price: Deepinfra ($0.18) and Hyperbolic ($0.20) offer the lowest output token prices for Qwen2.5 Coder 32B, followed by & Qwen2.5 Coder 32B, Fireworks.
Highlights
Quality
Artificial Analysis Quality Index; Higher is better
Speed
Output Tokens per Second; Higher is better
Price
USD per 1M Tokens; Lower is better
Parallel Queries:
Prompt Length:
Quality & Capabilities
Quality Evaluations (Preliminary Results)
Evaluation results measured independently by Artificial Analysis; Higher is better
Artificial Analysis Quality Index
Reasoning & Knowledge (MMLU)
Quantitative Reasoning (MATH)
Coding (HumanEval)
Artificial Analysis Quality Index: Represents the the average of each provider's results across evaluations.
Context Window
Context Window: Tokens Limit; Higher is better
Context window: Maximum number of combined input & output tokens. Output tokens commonly have a significantly lower limit (varied by model).
Variance between providers: While models have their own context window, in cases this is limited by providers.
Summary Analysis
Output Speed vs. Price
Output Speed: Output Tokens per Second; Price: Price: USD per 1M Tokens
Most attractive quadrant
Output Speed: 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: Price per token, represented as USD per million Tokens. Price is a blend of Input & Output token prices (3:1 ratio).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Latency vs. Output Speed
Latency: Seconds to First Tokens Chunk Received; Output Speed: Output Tokens per Second
Most attractive quadrant
Size represents Price (USD per M Tokens)
Output Speed: 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).
Latency: Time to first token of tokens received, in seconds, after API request sent. For models which do not support streaming, this represents time to receive the completion.
Price: Price per token, represented as USD per million Tokens. Price is a blend of Input & Output token prices (3:1 ratio).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Pricing
Pricing: Input and Output Prices
USD per 1M Tokens; Lower is better
Input price
Output price
Input price: Price per token included in the request/message sent to the API, represented as USD per million Tokens.
Output price: Price per token generated by the model (received from the API), represented as USD per million Tokens.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Speed
Measured by Output Speed (tokens per second)
Output Speed
Output Tokens per Second; Higher is better
Output Speed: 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).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Output Speed Variance
Output Tokens per Second; Results by percentile; Higher is better
Median, Other points represent 5th, 25th, 75th, 95th Percentiles respectively
Output Speed: 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).
Boxplot: Shows variance of measurements
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Output Speed, Over Time
Output Tokens per Second; Higher is better
Output Speed: 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).
Over time measurement: Median measurement per day, based on 8 measurements each day at different times. Labels represent start of week's measurements.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Output Speed by Input Token Count (Context Length)
Output Tokens per Second; Higher is better
100 input tokens
1k input tokens
10k input tokens
100k input tokens
Input Tokens Length: Length of tokens provided in the request. See Prompt Options above to see benchmarks of different input prompt lengths across other charts.
Output Speed: 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).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Latency
Measured by Time (seconds) to First Token
Latency
Seconds to First Tokens Chunk Received; Lower is better
Latency: Time to first token of tokens received, in seconds, after API request sent. For models which do not support streaming, this represents time to receive the completion.
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Latency Variance
Seconds to First Tokens Chunk Received; Results by percentile; Lower median is better
Median, Other points represent 5th, 25th, 75th, 95th Percentiles respectively
Latency: Time to first token of tokens received, in seconds, after API request sent. For models which do not support streaming, this represents time to receive the completion.
Boxplot: Shows variance of measurements
Latency, Over Time
Seconds to First Tokens Chunk Received; Lower is better
Latency: Time to first token of tokens received, in seconds, after API request sent. For models which do not support streaming, this represents time to receive the completion.
Over time measurement: Median measurement per day, based on 8 measurements each day at different times. Labels represent start of week's measurements.
Latency by Input Token Count (Context Length)
Seconds to First Tokens Chunk Received; Lower is better
100 input tokens
1k input tokens
10k input tokens
100k input tokens
Input Tokens Length: Length of tokens provided in the request. See Prompt Options above to see benchmarks of different input prompt lengths across other charts.
Latency: Time to first token of tokens received, in seconds, after API request sent. For models which do not support streaming, this represents time to receive the completion.
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Total Response Time
Time to receive 100 tokens output, calculated from latency and output speed metrics
Total Response Time vs. Price
Total: Response Time: Seconds to Output 100 Tokens; Price: Price: USD per 1M Tokens
Most attractive quadrant
Price: Price per token, represented as USD per million Tokens. Price is a blend of Input & Output token prices (3:1 ratio).
Total Response Time: Time to receive a 100 token response. Calculated based on Latency (time to receive first token) and Output Speed (output tokens per second).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Total Response Time
Seconds to Output 100 Tokens; Lower is better
Total Response Time: Time to receive a 100 token response. Calculated based on Latency (time to receive first token) and Output Speed (output tokens per second).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Total Response Time, Over Time
Seconds to Output 100 Tokens; Lower is better
Total Response Time: Time to receive a 100 token response. Calculated based on Latency (time to receive first token) and Output Speed (output tokens per second).
Over time measurement: Median measurement per day, based on 8 measurements each day at different times. Labels represent start of week's measurements.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
Total Response Time by Input Token Count (Context Length)
Seconds to Output 100 Tokens; Lower is better
100 input tokens
1k input tokens
10k input tokens
100k input tokens
Input Tokens Length: Length of tokens provided in the request. See Prompt Options above to see benchmarks of different input prompt lengths across other charts.
Total Response Time: Time to receive a 100 token response. Calculated based on Latency (time to receive first token) and Output Speed (output tokens per second).
Median: Figures represent median (P50) measurement over the past 14 days or otherwise to reflect sustained changes in performance.
Notes: Qwen2.5 Coder 32B, Fireworks: 33k context, Qwen2.5 Coder 32B, Deepinfra: 33k context
API Features
API Features: Function (Tool) Calling & JSON Mode
Function (Tool) Calling: Indicates whether the provider supports function calling in their API. Function calling is also known as 'Tool Calling'.
JSON Mode: Indicates whether the provider supports JSON mode in their API. When JSON mode is enabled, the models will always return a valid JSON object.
Summary Table of Key Comparison Metrics
Features | Price | Output tokens/s | Latency | |||
---|---|---|---|---|---|---|
Qwen2.5 Coder 32B | 131k | 70 | $0.20 | 35.5 | 0.52 | |
Qwen2.5 Coder 32B | 33k | 70 | $0.90 | 103.6 | 0.32 | |
Qwen2.5 Coder 32B | 33k | 70 | $0.18 | 54.2 | 0.25 |