Skip to content

Add debugging statements to startup code to profile it #12088

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
laurent22 opened this issue Apr 11, 2025 · 0 comments
Open

Add debugging statements to startup code to profile it #12088

laurent22 opened this issue Apr 11, 2025 · 0 comments
Labels
bug It's a bug desktop All desktop platforms high High priority issues

Comments

@laurent22
Copy link
Owner

laurent22 commented Apr 11, 2025

There have been more complains about the app being slow to start recently. Not sure if it's due to a recent change or something else but we should investigate.

  • We should add debug statements on starting code to find out which parts are slow
  • Then an option to enable/disable this feature (disabled by default)

Spec

  • We can use something like timerPush/timerPop from utils/time.ts to wrap statements. For example:
timePush('ClipperServer.instance().initialize');
ClipperServer.instance().initialize(actionApi);
timerPop();
  • All statements should be logged to a separate file in the profile folder, for example profiling.txt. timerPush/timerPop will have to be modified to log to file.
@laurent22 laurent22 added bug It's a bug desktop All desktop platforms high High priority issues v3.3 labels Apr 11, 2025
@laurent22 laurent22 assigned laurent22 and unassigned laurent22 Apr 11, 2025
@laurent22 laurent22 removed the v3.3 label Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug desktop All desktop platforms high High priority issues
Projects
None yet
Development

No branches or pull requests

1 participant