docs: record startup-time research; plan re-check after Fyne 2.7.x
Add docs/PERFORMANCE.md documenting the post-Phase-4 startup slowdown: the ~290ms increase is entirely Fyne 2.5.3->2.6.3's w.Show() cost, not the Service/domain/UI refactor. Includes the GOSENTRY_TIMING method and warm-run results table so it can be reproduced. Wire the startup re-measurement into the existing Fyne 2.6.3->2.7.x upgrade task in ROADMAP.md so 2.7's effect on w.Show() gets checked. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -35,6 +35,10 @@ window.
|
||||
- The project is currently on Fyne 2.6.3, so this depends on a Fyne 2.6.3 -> 2.7.x
|
||||
upgrade first (minor bump; re-verify the CGO build under MSYS2 UCRT64 and check
|
||||
for 2.7 breaking changes). Track the upgrade as its own task.
|
||||
- As part of that upgrade, **re-measure startup time** with the `GOSENTRY_TIMING`
|
||||
method recorded in [PERFORMANCE.md](PERFORMANCE.md). The Fyne 2.5.3 -> 2.6.3 bump
|
||||
added ~290 ms to startup, all inside `w.Show()`; check whether 2.7 recovers any
|
||||
of it or holds steady, and append the result to PERFORMANCE.md.
|
||||
- After upgrading, the change in `src/ui/run.go` (configureSystemTray) is small:
|
||||
call `desk.SetSystemTrayWindow(w)` alongside `SetSystemTrayMenu(menu)`. Keep the
|
||||
existing "Show" menu item, which the Fyne docs recommend for less-compliant
|
||||
|
||||
Reference in New Issue
Block a user