Measure first: a meeting with thousands of posts, and numbers to compare #225
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#225
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?
Groundwork for the 0.6 performance issues (D-057). Every fix there should come with a before/after number, not a feeling.
devseed: a few thousand posts, with long chains, wide threads (one post with hundreds of replies), and some pictures. The real meetings on kom.lysator.liu.se that number in the thousands are the model.performance.memory/ CDPRuntime.getHeapUsage);PerformanceObserver"longtask");/proc/PID/status) over the same walk, run from the desktop smoke harness.Merged in #252; main run #414 green.
tools/perf.sh LABELandtools/desktop-perf.sh LABELgive the numbers;tools/perf-table.py A Bcompares. Baseline table in #252. Each 0.6 PR since compares against it.