Comma-separated models to serve: tabicl, tabpfn, tabdpt, fake (no GPU or weights; for tests). The first is the default model. tabicl,tabdpt serves both from one cache.
TABCTX_DEVICES
auto
auto: every visible GPU, else the CPU. Or a list such as cuda:0,cuda:1. Two or more devices place each table on one GPU.
TABCTX_WORKER_PROCESSES
1
With several GPUs, one worker process per GPU (0: threads of one process).
TABCTX_GPU_MEMORY_FRACTION
1.0
The share of each GPU this server may use, in (0, 1]. Lower it when replicas share a GPU.
TABPFN_TOKEN
Needed to download TabPFN weights, after accepting Prior Labs' terms.
A directory for the disk tier: evicted contexts are written here and restored on their next predict. Measure on your disk first; a re-fit can be faster than a restore from a slow one.
TABCTX_SPILL_CAPACITY_BYTES
50 GiB
The disk tier's size, shared across GPUs.
TABCTX_KV_CACHE
kv
TabICL's context: kv (fastest predicts), repr (much less memory per context), off (re-encode on every predict).
TABCTX_KV_PRECISION
int8
TabICL's cached keys and values: int8 (about half the memory; identical labels and metrics on 7 datasets, probabilities within 0.01), fp16, native.
TABCTX_OFFLOAD_DIR
<spill dir>/offload
Where TabICL may stage a very large fit's intermediate results on disk.
No fitted table is kept longer than this after its fit: it is deleted from device memory, host memory and the disk tier, within 30 s. It applies to every table, including those fit before it was set (a table spilled by tabctx < 0.19 has no recorded fit time and counts as expired). A fit can ask for less with ttl_s; GET /v1/tabctx/limits reports it.
true, 1 or yes: every request that reads or changes contexts must carry x-tabctx-tenant-id (else 401). /v1/tabctx/limits, /v1/models and the probes don't need it.
RAY_SERVE_SESSION_ID_HEADER_KEY
x-session-id
The replica-affinity header, shared with Ray Serve's router.
The tenant header is trusted as sent
tabctx does not authenticate callers: any caller can send any tenant
id. Tenancy is a security boundary only behind a gateway that
authenticates each caller, sets x-tabctx-tenant-id itself and
strips any value the client sent. See
tenant isolation.