An AI system has to fit the data, hardware, budget, and people operating it. I work across those layers, from a focused software implementation to infrastructure and deployment involving several teams.

From a problem to an implementation

Slow inference might be a model problem, a batching problem, or a hardware bottleneck. Unreliable results might start in the data pipeline. I investigate the actual failure before choosing what to change.

My work includes production data pipelines, LLM systems, and an in-house GPU experimentation lab. I can implement independently, join your engineers, or lead the team. Selected work describes my contribution to those systems.

Architecture & deployment

Deployment decisions affect how you evaluate a model, observe failures, release changes, and recover when something goes wrong. Local inference adds hardware and capacity constraints. I work through those decisions with the people who will build and operate the system.

Services and rates cover implementation, technical leadership, and discovery. To discuss the work, book a call or email me.

Headroom

Spare capacity changes how a system responds to more traffic. This idealized M/M/1 queue compares two starting points under the same 10% increase in arrival rate. It is not a benchmark of a client system.

Latency under load: M/M/1 queueing curve Mean latency as a multiple of base service time, as a function of utilization, following the M/M/1 queueing formula latency = 1/(1-utilization). A system running at 55% utilization and one running at 90% both absorb the same 10% traffic increase differently: the provisioned system's latency rises 14%, from 2.2x to 2.5x base service time; the reactive system's latency rises 900%, from 10.0x to 100.0x, off the plotted scale. 25% 50% 75% 90% 1x 2x 4x 6x 8x 10x 12x utilization (arrival rate / capacity) latency (× base service time) provisioned · 2.2x reactive · 10.0x +10% traffic -> 2.5x +10% traffic -> 100x, off chart
fig. 1 · mean time in an M/M/1 system, relative to mean service time: 1/(1−utilization). A 10% increase in traffic takes utilization from 55% to 60.5%, increasing latency by about 14%. Starting at 90%, the same increase takes utilization to 99% and raises latency by 900%, beyond the chart's vertical scale.

Azu

AI agent

1 of 3 · Introduction

Chat about this page

Azu is an AI agent that runs locally on your device. You can chat with Azu and ask questions about the current page. No chat data leaves your device.