-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
Legendary slowness on macOS precompiled binary #581
Comments
This issue is still present. |
This is largely due to PyInstaller just being not all that great for CLI apps (on Windows/Linux it does better, on macOS it's really slow for some reason). Perhaps using https://github.com/indygreg/PyOxidizer will help there, I plan to investigate that in the future. Also worth noting that current macOS builds should not be universal, they are x86 only. |
hmm |
macOS binaries are currently created on CI, see https://github.com/derrod/legendary/blob/master/.github/workflows/python.yml |
k I did some further investigation and apparently it has something to do with pyinstaller's bootloader when "--onefile" is specified as a command. It's slow because it has to unpack the libraries "just-in-time", instead of fully compiling it beforehand. |
tldr: it's slow because it has to do an extra step before running |
Any way to install legendary without this really slow startup time from "one file" mode? |
Platform
Operating system and version: macOS 14 | beta 2
Legendary version (
legendary -V
): 20.33, Undue AlarmExpected Behavior
After typing a command into the terminal, the expected response should take milliseconds.
Current Behavior
legendary status --offline
takes 6 seconds to return an output.it's even longer when trying to launch a game (< 30s)
Steps to Reproduce
Additional information
The text was updated successfully, but these errors were encountered: