Build a Local Open-Weight Model Quantization Profiling Workspace
Benchmark open-weight models across FP8, INT8, and INT4 precisions on local developer test rigs. Evaluate memory footprint and perplexity tradeoffs to recommend target deployment configs.
What you are building
The core problem, expected build, and operating context for this challenge.
Benchmark open-weight models across FP8, INT8, and INT4 precisions on local developer test rigs. Evaluate memory footprint and perplexity tradeoffs to recommend target deployment configs.
Edge Deployment Engineer
Profile open-weight model weights using local Ollama or vLLM open runtimes.
Measure VRAM consumption, memory bandwidth saturation, and tokens-per-second.
Call hosted Claude to evaluate quantization degradation reports and operational limits.
Output an optimized deployment recommendation manifest for edge hardware.
Local web UI showing precision comparison radar charts, latency distributions, and exportable config manifests.
Use open-weight small models (e.g. Qwen-1.5B or Llama-3-8B) with standard synthetic calibration texts. Starter examples below are synthetic. They are not downloaded records.
vLLM open-model serving Applies vLLM quantization format specifications (FP8, INT8, INT4, AWQ) to structure memory benchmark comparisons.
ollama, anthropic-claude, pydantic-ai. Provides a clean local execution environment to benchmark open-weight model quantization variants without cloud dependencies. Hosted Claude API for cross-precision degradation analysis. Local execution strictly for open-weight test models.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Profiles at least two quantization precisions of an open-weight model on local test hardware.
Measures token latency and active memory footprint accurately.
Generates structured JSON hardware deployment specifications via Claude API.
```json [ { "input": { "model_name": "Qwen2.5-7B", "available_vram_gb": 12, "benchmark_results": [ { "precision": "FP16", "vram_used_gb": 14.2, "tps": 22.1, "eval_loss": 2.14 }, { "precision": "INT4_AWQ", "vram_used_gb": 5.8, "tps": 48.5, "eval_loss": 2.21 } ] }, "expected_output": { "selected_precision": "INT4_AWQ", "fit_status": "fits_with_headroom", "kv_cache_headroom_gb": 6.2, "performance_gain_pct": 119.4, "deployment_flag": "--quantization awq --gpu-memory-utilization 0.9" } }, { "input": { "model_name": "Llama3-8B", "available_vram_gb": 4, "benchmark_results": [ { "precision": "INT4_AWQ", "vram_used_gb": 5.6, "tps": 32, "eval_loss": 2.3 } ] }, "expected_output": { "selected_precision": "none", "fit_status": "insufficient_vram", "kv_cache_headroom_gb": 0, "performance_gain_pct": 0, "deployment_flag": "Requires minimum 8GB VRAM or CPU offload" } } ] ```
Operates only on open-weight models in local sandboxes; never attempts to load or quantize proprietary Claude weights. Use mock external writes. Require human review before any real deployment.
Participation guide
Operates only on open-weight models in local sandboxes; never attempts to load or quantize proprietary Claude weights. Use mock external writes and human review.
How work is evaluated
Profiles at least two quantization precisions of an open-weight model on local test hardware. Measures token latency and active memory footprint accurately. Generates structured JSON hardware deployment specifications via Claude API.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Profile open-weight model weights using local Ollama or vLLM open runtimes. Measure VRAM consumption, memory bandwidth saturation, and tokens-per-second. Call hosted Claude to evaluate quantization degradation reports and operational limits. Output an optimized deployment recommendation manifest for edge hardware.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Profiles at least two quantization precisions of an open-weight model on local test hardware. Measures token latency and active memory footprint accurately. Generates structured JSON hardware deployment specifications via Claude API.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Local web UI showing precision comparison radar charts, latency distributions, and exportable config manifests.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Operates only on open-weight models in local sandboxes; never attempts to load or quantize proprietary Claude weights.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Profile open-weight model weights using local Ollama or vLLM open runtimes.
Measure VRAM consumption, memory bandwidth saturation, and tokens-per-second.
Call hosted Claude to evaluate quantization degradation reports and operational limits.
Output an optimized deployment recommendation manifest for edge hardware.
Reference links and supporting material
Use open-weight small models (e.g. Qwen-1.5B or Llama-3-8B) with standard synthetic calibration texts. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Ollama
Local LLM runtime for offline inference.
Evaluated output
No output checks are configured.
- Profile open-weight model weights using local Ollama or vLLM open runtimes. Measure VRAM consumption, memor...
- Profiles at least two quantization precisions of an open-weight model on local test hardware. Measures toke...
- Local web UI showing precision comparison radar charts, latency distributions, and exportable config manife...
- 2 public reference cases
- 1 configured tool
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Ollama · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.