This is really interesting (to an observer, maybe that's not the word you'd use). PyInstaller doesn't do anything that should cause this. It collects all imported modules into a special archive that is part of the executable. It makes a local copy of the Python interpreter, also part of the executable. At startup, the bootloader launches the embedded Python and sets up its import mechanism so all imports are executed by pulling from the embedded archive. That's it! But those imports should take no more time to execute than a normal import. And anyway, importing is normally only done once, starting up.
When dealing with a file that big, and large memory allocation, some small change in the mode of operation could have a big impact. Somehow the cache-alignment gets wrong and suddenly you are doing 10x the number of memory accesses. Or some buffer is smaller and you are doing 10x as many file reads. Or the program has a smaller virtual memory allocation and suddenly it is "thrashing" to the backing store. Something like that. Not much help, I know. -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
