A BYOC container that works locally may fail in production under concurrent sessions, GPU memory pressure, or ungraceful restarts. Use this checklist to verify container behaviour before registering on mainnet.Documentation Index
Fetch the complete documentation index at: https://na-36-handover-docs-v2-into-docs-v2-dev-20260518.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
GPU memory profiling
Profile your container under the expected concurrent session count:maxSessions configuration.
Graceful shutdown
The orchestrator sendsSIGTERM when stopping a container. Handle it:
SIGTERM is killed after a timeout (default 10 seconds). Active sessions receive no graceful close and may produce incomplete output.
Health check under load
The/health endpoint must return {"status": "ok"} even under full GPU load. If health checks fail, the orchestrator stops advertising the capability and gateways route elsewhere.
Common failure: the health check handler shares the GPU inference thread and blocks during heavy processing. Run health checks on a separate thread or async task.
Monitoring
Expose Prometheus metrics from your container for the orchestrator’s monitoring stack:| Metric | Description |
|---|---|
byoc_sessions_active | Current concurrent sessions |
byoc_frame_latency_ms | Per-frame processing latency histogram |
byoc_gpu_memory_bytes | Current GPU memory usage |
byoc_errors_total | Processing errors by type |