If your application is slow at coming up, that will be true without PyInstaller as well. PyQt is generated by SIP which generates very fast lazy bindings importing the whole PyQt is faster than any other GUI library because it basically does nothing: all bindings to classes/functions are dynamically created when (and if!) you access them, saving lots of memory too. On Windows, I/O is very slow, and then you have antiviruses that will want to double check all those DLL files. PyInstaller's bootloader is usually quite fast in one-dir mode, but it can be much slower in one-file mode, because it depacks everything into a temporary directory. This way you can get a clear picture whether the time is spent in PyInstaller's bootloader or in your application. When I launch any game portal 2, fallout 4, banished the only thing in the oculus that shows up in oculus home. Then run your packaged executable from the command line. When I launch as admin, perception.exe V4.0.0 I get 3 drop downs, choose oculus rift direct mode - 111 in the first, oculustrack - 40 in the second and primary monitor in the 3rd, the 4th show oculus profile:default.
Vorpx .exe taking too long code#
This gives you a working console you can use for debugging.Īt the top of your main script, even before the first import is run, add a print "Python Code starting". Tell PyInstaller to create a console-mode executable. If I need to, I could probably edit the PyInstaller loader stub to create a window, but that's another route i'd rather not take. I'd like to avoid adding a splash screen for two reasons - one, I expect it won't help (the overhead is before Python code runs) and two, I just don't like splash screens :) What is the generally accepted technique for reducing time until the first window is shown? How can I measure the time spend i the first few seconds of the process's lifetime?
How can I make this application start faster? I have access to the source for the PyInstaller win32 loader, the Python code, and even the launcher code. When my application shows it's window, it cannot come to the foreground due to the rules for SetForegroundWindow. The user will click the button to launch the app, see nothing appear to happen, and click elsewhere on another application. The problem is that this application is started with a custom laucncher / taskbar application. Instead, I suspect this is due to the Python runtime initializing. As far as I can tell, this is not due to slowness in my code. Running this application has a delay of about 10 seconds before the main window loads and is shown. I have an application written in Python and 'compiled' with PyInstaller.
0 kommentar(er)
