RE: [Py2exe-users] Re: (Code, long!) was: Re: A faster modulefinder

[Schollnick, B. <Benjamin.Schollnick@XEROX.COM>]

> > It's well worth it for me.  I reduced the Auditor=20
> application loading=20
> > time by roughly 26 seconds...  That uses wxPython,=20
> PythonCard, and a=20
> > variety of other technologies, so it's no light weight... (And is=20
> > roughly 5-6 Meg compressed in a ZIP)
>=20
> That's totally bogus, modulefinder has nothing to do with runtime.  =20
> If your application starts faster, it's because Windows is caching =20
> something so you spend less time waiting on disk.

Bob,

I can't discount completely Windows caching something that is not
suppose to....  But these applications are containing in a
self-contained, self-unarchiving ZIP file....

So the only change  I made between 3.10 & 3.10a was the addition of the
ModuleFinder  patch...

Now, there is defintely a speed increase in v3.10a.  Since the only
change I can attribute this to is the ModuleFinder patch, I must assume
it is the MF patch...

This was on 4 computers, with only a single system having Python
installed.
In some of the cases they ran v3.10 before v3.10a...  Other cases they
only ran v3.10a

I tried to do a quick profile to ensure that ModuleFinder is being used
during execution of the PY2exe built application, but failed....

I simply do not see how Windows could be caching anything if the files
it was caching were completely overwritten.... by files that have a
different time/date stamp.

	- Ben