-
-
Notifications
You must be signed in to change notification settings - Fork 296
Use Registry to speed Autostart up #1469
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
base: master
Are you sure you want to change the base?
Conversation
cfe20c4 to
284a6bb
Compare
Use shell:startup by default instead of registry, with the option to autostart via registry using the --registry flag
|
The speed of the Autostart feature was one of the primary factors that I almost dropped Komorebi, but I figured I owed it to myself to see if I could improve on it seeing as similar applications such as SeelenUI are already running by the time you land on your desktop after logging in. I've been able to get Komorebi to load by least 5 seconds after login by creating a Scheduled Task to run the
|
I did consider Task Scheduler for this PR as its very very quick to execute its tasks, but i felt like that might be a bit too invasive for users. Thats why i opted into the windows-recommended way of starting programs via registry |
07b6367 to
b613986
Compare
I've noticed that the startup can sometimes be a bit slow.
So i have decided to try to speed the autostart up a bit, by adding the startup entry in the Registry instead of using shell:startup.
The PR also:
(old startup entries referring to the shell:startup method)
The Tests show an average startup improvement time of 6s across 3 runs each, despite strong variations and inconsistencies due to the nature of windows' boot process.
29,3s p. average for
shell:startup22,9s p. average for
registryEDIT: the registry autostart is now locked behind the --registry flag.
By default, shell:startup is used and will (when enabled) also attempt to remove the komorebi autostart registry entry if it exists.
When the --registry flag is used, it will first try to remove the shell:startup shortcut (if it exists) and then create the appropriate registry startup entry.