Performance review of the whole codebase #230
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#230
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User, 2026-10-21 (D-058): "When you're done with the issues I gave you. I want you to also make a general investigation into the codebase and see where we can get improvements in performance and resource usage. Things are relatively heavy as they are now"
After #225–#229: go through the client library, the app, the relay and the build (binary and wasm size, startup, idle CPU, network round trips, allocations, the web image). File what is worth doing as separate issues in 0.6, with the measured or estimated gain.
Review done; what it found is filed in 0.6:
Checked and fine as they are: Caddy compresses (zstd/gzip) and caches the hashed assets forever; the protocol decoder scans incrementally; the relay forwards bytes without parsing; the keepalive interval.