mirror of
https://github.com/mostlygeek/llama-swap.git
synced 2026-06-09 06:46:34 +02:00
Benson Wong
02e015fa49
This is a huge backend change that essentially started with rewriting the concurrency handling for processes and blew up to a refactor of the entire application. In short these are the improvements: **Better state and life cycle management:** Life cycle management of processes has always been the trickiest part of the code. Juggling mutex locks between multiple locations to reduce race conditions was complex. Too complex for my feeble brain to build a simple mental model around as llama-swap gained more features. All of that has been refactored. Most of the locks are gone, replaced with a single run() that owns all state changes. There is one place to start from now to understand and extend routing logic. The improved life cycle management makes it easier to implement more complex swap optimization strategies in the future like #727. **Collation of requests:** llama-swap previously handled requests and swapping in the order they came in. For example requests for models in this order ABCABC would result in 5 swaps. Now those requests are handled in this order AABBCC. The result is less time waiting for swap under a high churn request queue. This fixes #588 #612. A possible future enhancement is to support a starvation parameter so swap can be forced when models have been waiting too long. **Shared base implementation for groups and swap matrix:** During the refactor it became clear that much of the swapping logic was shared between these two implementations. That is not surprising considering the swap matrix was added many moons after groups. Now they share a common base and their specific swap strategies are implemented into the swapPlanner interface. Requests for bespoke or specific swapping scenarios is a common theme in the issues. Now users can implement whatever bespoke and weird swapping strategy they want in their own fork. Just ask your agent of choice to implement swapPlanner. I'll still remaining more conservative on what actually lands in core llama-swap and will continue to evaluate PRs if the changes is good for everyone or just one specific use case. **AI / Agentic Disclosure:** I paid very close attention to the low level swap concurrency design and implementation. It's important to keep that essential part reliable, boring and no surprises. Backwards compatibility was also maintained, even the one way non-exclusive group model loading behaviour that people have rightly pointed out be a weird design decision. With the underlying swap core done the web server, api and UI sitting on top were largely ported over with Claude Code and Opus 4.7 in multiple phases. If you're curious I kept the changes in docs/newrouter-todo.md. I did several passes to make sure things weren't left behind. However, even frontier LLMs at the time of this PR still make small decisions that don't make a lot of sense. They get shit wrong all the time, just in small subtle way. That said, there's likely to be some new bugs introduced with this massive refactor. I'm fairly confident that there's no major architectural flaws that would cause goal seeking agents to make dumb, ugly code decisions. For a little while the legacy llama-swap will be available under cmd/legacy/llama-swap. The plan is to eventually delete that entry point as well as the proxy package. On a bit of a personal note, this PR is exciting and a bit sad for me. I hand wrote much of the original code and this PR ultimately replaces much of it. While the old code served as a good reference for the agent to implement the new stuff it still a bit sad to eventually delete it all.
86 lines
1.9 KiB
Go
86 lines
1.9 KiB
Go
// Package configwatcher provides a simple cross-platform file watcher based
|
|
// on os.Stat polling. It works correctly inside Docker containers where the
|
|
// config file is bind-mounted as an individual file, and for k8s ConfigMap
|
|
// projections (which present the file as a symlink to an atomically swapped
|
|
// target) — both cases where inotify-based watchers are unreliable.
|
|
package configwatcher
|
|
|
|
import (
|
|
"context"
|
|
"errors"
|
|
"io/fs"
|
|
"log"
|
|
"os"
|
|
"time"
|
|
)
|
|
|
|
const DefaultInterval = 2 * time.Second
|
|
|
|
type Watcher struct {
|
|
Path string
|
|
Interval time.Duration
|
|
OnChange func()
|
|
}
|
|
|
|
type snapshot struct {
|
|
exists bool
|
|
modTime time.Time
|
|
size int64
|
|
}
|
|
|
|
// Run blocks until ctx is canceled. It polls Path on Interval and invokes
|
|
// OnChange whenever the file's modification time or size changes, or when
|
|
// the file reappears after being missing. The baseline poll establishes
|
|
// initial state and does not fire OnChange.
|
|
func (w *Watcher) Run(ctx context.Context) {
|
|
interval := w.Interval
|
|
if interval <= 0 {
|
|
interval = DefaultInterval
|
|
}
|
|
|
|
prev := stat(w.Path)
|
|
|
|
ticker := time.NewTicker(interval)
|
|
defer ticker.Stop()
|
|
|
|
for {
|
|
select {
|
|
case <-ctx.Done():
|
|
return
|
|
case <-ticker.C:
|
|
cur := stat(w.Path)
|
|
if changed(prev, cur) && w.OnChange != nil {
|
|
w.OnChange()
|
|
}
|
|
prev = cur
|
|
}
|
|
}
|
|
}
|
|
|
|
func stat(path string) snapshot {
|
|
fi, err := os.Stat(path)
|
|
if err != nil {
|
|
if !errors.Is(err, fs.ErrNotExist) {
|
|
log.Printf("configwatcher: stat %s: %v", path, err)
|
|
}
|
|
return snapshot{}
|
|
}
|
|
return snapshot{
|
|
exists: true,
|
|
modTime: fi.ModTime(),
|
|
size: fi.Size(),
|
|
}
|
|
}
|
|
|
|
func changed(prev, cur snapshot) bool {
|
|
// Present → missing: stay quiet (likely a transient rename-style write).
|
|
// Missing → present: fire so we reload as soon as the file comes back.
|
|
if !cur.exists {
|
|
return false
|
|
}
|
|
if !prev.exists {
|
|
return true
|
|
}
|
|
return !prev.modTime.Equal(cur.modTime) || prev.size != cur.size
|
|
}
|