You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It feels like it takes perhaps an extra half second for a command like "gdh" to launch the gvc.app ever since the CLI started creating a .app shell on demand.
Things to check:
Perhaps gvc is failing to cache a .app that is already created, unnecessarily recreating it on every CLI call
Things to do:
Add performance tests around how long it takes for a gvc CLI command to launch & show a window in gvc.app
Suggest add end-to-end wall clock profile that (1) is captured on each CI run and (2) is graphed against historical CI runs automatically in the generated per CI run report
Suggest add deterministic performance test that mocks the CLI's dependencies and counts the number of "expensive" operations that are performed
It feels like it takes perhaps an extra half second for a command like "gdh" to launch the gvc.app ever since the CLI started creating a .app shell on demand.
Things to check:
Things to do: