Prefill and token generation speed

Qwen Flash Next on two DGX Sparks: what changes?

Explore Qwen3.8 Flash Next on two DGX Sparks. Compare the same model on one unit and separate added model capacity from single-response generation speed.

Benchmark-based estimate · 4K input · one user

Last updated

16.7 ~ 33.8 tok/sDecode speed
Model fully loaded (107.13GB / 232GB)
First token (TTFT)
1.7 to 4.3 secondsContext 4,096 input tokens included
Prefill speed
973 ~ 2,517 tok/s1.6 to 4.2 seconds (Estimation based on public benchmarks)
Total time (E2E)
Approximately 5.1 to 11.2 seconds117 output tokens included
Press Play to process the input and generate the answer.
Ready
Change device or model
546 GB/s combined
Active 6B / Sangju 180B
Expand settings 4-bit · 4K · Baseline decode
QuantizationNeed 107.13GB
Input context4K tokens
Baseline
Baseline
Sample question:
117 output tokens

Reading this result

Two units are connected nodes, not one memory pool. Partitioning and interconnect conditions affect results, and settings for one fast request differ from those for throughput. This screen simulates a single request.

Required / available memory
107.1GB / 232GB
Runtime
4-bit · 2-node setup

Compare this model side by side

Compare from prefill against one unit. If a second unit does not speed up a single answer as much as you expect, reconsider whether your goal is larger models or concurrent throughput.

Check configuration

2× DGX Spark 256GB · Memory 256GB

Qwen3.8-Flash-Next Q4_K_M configuration. Check that the retailer lists the same memory option.

What changes with a longer document?Expand input length, waiting time, speed and memory
Detailed analysis and all 60 hardware configurations

Popular configurations

View all 20