# miracache: frequently asked questions

> Source: the FAQ on https://www.mirastacklabs.ai/miracache/ (generated at build time, 2026-11-19). The repo has no docs/faq.md yet; this file switches to it automatically when it appears.

## Do we need to change vLLM or SGLang?

No. Zero changes to either engine: both load miracache as a plug-in through configuration flags only.

## Do we need a lossless (PFC) network?

No. iWARP runs on plain Ethernet. ConnectX-6 Dx and newer are profiled for Zero-Touch RoCE (not yet verified on hardware). If you control your switch, PFC with ECN is supported too.

## Can we use InfiniBand?

Not yet. miracache runs on RoCE v2 and iWARP over Ethernet. ConnectX cards that also support Ethernet work when switched to Ethernet mode on an Ethernet switch.

## Which model will we run?

The model is chosen by the GPUs you bring. Every on-versus-off comparison uses the same model and settings on both sides.

## Do the memory servers need GPUs or fast CPUs?

No. They serve reads with no CPU work on the data. Memory capacity and the network card matter most.

## Why not cache on local NVMe instead?

NVMe is cheaper per TB but slower per read, wears out under constant rewrites, and only its own server can use it. The shared DRAM pool is faster, serves every GPU server and keeps a session’s state when it moves. NVMe works well as a lower tier for cold sessions.

## How do I install it?

Start with the [README on GitHub](https://github.com/mirastacklabs-ai/miracache#readme).

## What if our servers are PCIe Gen3?

They are welcome. A Gen3 x16 slot carries one 100G port at full speed.
