# Blog
URL: https://viiwork.pulu.app/blog/
Updated: 2026-10-27

- [Two RTX 5090 hosts sharing a KV cache over Ethernet](https://viiwork.pulu.app/blog/kv-share-two-5090-hosts/): What a KV cache is, why moving a coding-agent session between GPU hosts is expensive, and how much a faster link helps viiwork's kv_share keep those switches warm — measured on two RTX 5090 hosts.
- [Why coding agents need session affinity](https://viiwork.pulu.app/blog/session-affinity-coding-agents/): An overnight agent swarm showed what happens when a conversation keeps moving away from its prompt cache, and why pinning a machine is only part of the answer.
- [How the viiwork mesh routes a request](https://viiwork.pulu.app/blog/how-the-mesh-routes-requests/): Any viiwork node accepts a request for any model in the mesh. This post follows one request from discovery and capacity reports to the slot that runs it.
- [Bringing a new machine into a viiwork mesh](https://viiwork.pulu.app/blog/bringing-a-node-online/): What the viiwork setup wizard checks, proposes and writes when it turns a machine with GPUs and GGUF files into a node, and how the next machine joins.
- [Where viiwork came from](https://viiwork.pulu.app/blog/where-viiwork-came-from/): viiwork began as a pile of secondhand GPUs and one llama.cpp process per model. This is the story of how a wall of hand-written peer lists and ports became a mesh that forms itself.