-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
startup speed is slow. #125
Comments
After the system starts, the first time I see the picture, the startup speed is slow. |
@cmhdream can you upload the picture in question here |
I think this is because the program is not started first when booting. |
I was just trying to see if there are some elements that could otherwise influence this behaviour. My best guess is that the .net runtime takes time to start + the jit compiler just needs time to convert il to machine code in otherwords there're not many ways to fix this :/ |
In the 2.2 version, I've optimized the startup procedure to load the visual elements first and the rest later, to make it feel faster. Additionally, I'm currently working on rewriting from WPF to the Avalonia platform (and also add macOS support). It will take a while to convert it, but when it's completed, you can expect a new version with smoother performance and start-up time. |
PicView 2.2.1 .net 8 version. It seems a little faster. |
There's a new preview version out, that has improved startup time, as discussed above. It's a complete rewrite, that is being actively developed. Head to https://picview.org/avalonia-download to try the new preview versions. |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: