Performance
Memory
Krust typically uses ~80–91 MB of RAM (verified via Activity Monitor). For comparison:
- Lens — 800 MB to 2 GB
- Aptakube — ~1.5 GB (5 processes)
- k9s — ~120 MB
- Krust — ~80–91 MB
Startup
Cold start completes in under 1 second. Lens typically takes 5–30 seconds to become usable.
Rendering
Krust handles 1,500+ pods at a smooth 60 fps. The pod list uses NSTableView, which renders only the ~30 visible rows — O(visible) rather than O(total). Full table recreation completes in 30 ms.
Log Performance
Logs are stored in a 100K line ring buffer in Rust. Full-text search completes in under 15 ms with no UI thread blocking.
Why It's Fast
Krust avoids the overhead that slows down other tools:
- No Electron or web runtime
- No JavaScript
- No garbage collector
- Rust for all data processing
- Swift and AppKit for native rendering
- Zero-copy snapshots between Rust and Swift