DevelopingDad's picture
Update weight-only checkpoint and generic DGX Spark serving package
231d9a6 verified
|
Raw History Blame Contribute Delete
2.91 kB

Generic native API screen — October 23, 2026

This is a fresh, self-contained diagnostic of the weight-only NVFP4/FP8 target with higher-precision activations, MTP8 and FP8 KV on one NVIDIA DGX Spark GB10. It runs directly against a native vLLM 0.31.0 API, using the native chat-template behavior with system-block whitespace compatibility. No external datasets, custom instructions, automatic repairs or application middleware are used. The model server was already warm.

The measured serving settings were 65,536 total tokens, eight slots, 4,096 batched tokens, 60 GiB FP8 KV and prefix caching enabled. The three measured generation requests were sequential and used a unique cache_salt to prevent prefix reuse. This is not a concurrency or long-context test.

Prompt Prompt tokens Completion tokens First content, seconds Approximate completion tok/s after first content Finish
explanation 33 512 0.076 55.0 length
comparison 37 512 0.065 59.7 length
code 40 512 0.123 89.1 length

All three generation requests reached their 512-token ceiling. These numbers measure capped generation only and do not establish complete or correct answers. The rate divides reported completion tokens by the interval from first visible content to stream completion; usage may include terminal/control tokens. It is not the conservative delivery calculation from the earlier package. No median, minimum, warmup exclusion or statistical speedup is inferred from three rows.

Four bounded protocol/function checks passed:

  • Opt-in reasoning on one arithmetic expression, with a 2,048-token thinking cap and 4,096-token total completion allowance; correct final integer.
  • Explicit strict JSON-schema response.
  • Forced generic function call with the expected argument.
  • Continuation from a synthetic function result.

These are deliberately small checks. They do not establish broad arithmetic, tool-selection, instruction-following, factual or multimodal quality. Generic results contain counts, timing and verdicts, not deployment identifiers.

Reproduce

After starting the native server:

python3 benchmarks/evaluate.py --base-url http://127.0.0.1:8000/v1 --output generic-results.json

The script uses only Python's standard library. It issues seven completion requests: three generation probes and four function/protocol checks. Request schemas and prompts are in the script. A failed check gives a nonzero exit code. Use results.json for the saved machine-readable receipt.

Target tensor/config hashes are recorded in the artifact manifest and tensor integrity report. The portable launcher was checked without restarting the measured server; this receipt does not claim a new GPU start of the exact portable wrapper.