An immersive LLM experience cannot depend on a remote API when users have poor service or no internet access. Edge computing moves inference onto a device near the user. It can also avoid the network round trip and third-party availability problems that matter in latency-sensitive applications. Running an LLM on an edge device is possible, but remains exploratory. section 1.2.2
The immediate constraints are memory and speed. An edge device with 8 GB of RAM and no GPU may struggle to deliver even one token per second; there is no uniformly good fix. Edge devices can support ML development and inference, but training an LLM on one is not a practical target here. section 6.4
Choose hardware and model format together:
- A Raspberry Pi can gain inference capacity from a Coral USB TPU, though USB 3.0 bandwidth limits it. TPU use requires converting the model and inference code to TensorFlow; Optimum can convert models to TensorFlow Lite format. section 6.4
- A Jetson-style board includes a GPU and CUDA, avoiding the separate accelerator purchase and the TensorFlow requirement. ExecuTorch is another offering for edge inference. section 6.4
Use edge deployment when connectivity or response time makes an API unsuitable, but budget for the device’s memory, compute, and conversion requirements. Quantization and other parameter-efficient methods are part of the surrounding effort to make local LLM use feasible; they do not erase the hardware trade-offs. section 1.2.2 section 6.4




