Salesforce · Codegen2
codegen2-16B_P
Unverified · community-discovered, not yet reviewedcodegen2-16B_P is a discovered model from public model catalogues. Badgr builds a GPU serving profile from source metadata, estimated VRAM, context length, and available execution routes.
Last validated or meaningfully updated: Dynamic source discovery
Availability
Not yet Badgr AI API
Not currently validated
✓ Dedicated endpoint
Available through Badgr
✓ Custom GPU deployment
Available through Badgr
Deployment profile
- Architecture
- Source metadata pending
- Minimum VRAM
- ~36GB
- Context
- Source dependent
Recommended: L40S 48GB. VRAM is an estimate and increases with context, cache, concurrency, and runtime overhead.
Model identity
- Updated
- 1 years ago
- HuggingFace revision
- 14bcc89999
Popularity and trust
Downloads (last month)
37.4K
Likes
45
Spaces using this model
8
Files and formats
Weight formats
PyTorch bin
Repository files
19
Tokenizer
BPE
Chat template
Available
This repo ships custom modeling code (trust_remote_code required to load with Transformers).
GPU deployment scenarios
Estimated from parameter count and quantisation. Will switch to “Verified by Badgr” once a real run backs a tier.
Testing
L40S 48GB
Short context, low concurrency
Small production
A100 80GB
8K context, 1-4 concurrent requests
Higher throughput
H100 80GB
32K context, continuous batching
Large production
L40S 48GB
Higher concurrency
Estimated — multimodal inputs, long context, and concurrency all increase real VRAM use beyond this estimate.
Also runs well on A100 80GB, H100 80GB. Available in United States, Europe, Asia Pacific.
Serving compatibility
| Runtime | Status | Notes |
|---|---|---|
| vLLM | Estimated | Used for Badgr dedicated endpoints |
| Transformers | Declared by source | Basic fallback |
| llama.cpp | Requires GGUF conversion | No GGUF weights found in repo |
| SGLang | Unknown | Not evaluated |
| TensorRT-LLM | Unknown | Conversion may be required |
| TGI | Unknown | Not evaluated |
Ready-to-run Badgr configurations
Quick test
badgr serve Salesforce/codegen2-16B_P --max-cost 2Dedicated endpoint command
badgr serve Salesforce/codegen2-16B_P --gpu L40S --max-cost 10Advanced configuration (defaults to automatic)
- Runtime
- Quantisation
- GPU and GPU count
- Context length
- Maximum concurrency
- Region
- Maximum hourly spend
- Persistent or capped runtime
Estimated pricing
Provider estimate: cold start
3–6 min
Provider estimate: endpoint cost
$0.75 – $0.75/hr
Idle cost
$0 when stopped
Per-token throughput cost is not shown here: Badgr has not benchmarked this model yet, and this page does not display figures it cannot back with real data.
Recommended Badgr routes
L40S 48GB · Europe
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
L40S 48GB · Europe
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
L40S 48GB · Europe
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
L40S 48GB · Asia Pacific
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
L40S 48GB · Asia Pacific
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
L40S 48GB · Asia Pacific
Estimatedstarting from $0.75/hr
Badgr estimated starting price
Best for
ComfyUI, vLLM Endpoint, Qwen 2.5 7B Instruct
Startup: 3–6 min
Reliability: Good
Last checked: Live marketplace price not available yet
Known limitations
- Source-discovered pages use best-effort metadata from an automated publication gate, not manual review.
- Licence, gated access, runner compatibility, and exact memory use should be checked before production deployment.