-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Florian Schulze wrote:
Log message for revision 90415: Don't pin setuptools. Moved zope3.cfg to versions-zope3.cfg. Added some missing files from the Zope2 trunk. Added dummy script which will be used to create lib/python.
<snip/>
Modified: Zope2.buildout/trunk/buildout.cfg
--- Zope2.buildout/trunk/buildout.cfg 2008-08-27 09:32:04 UTC (rev 90414) +++ Zope2.buildout/trunk/buildout.cfg 2008-08-27 09:33:59 UTC (rev 90415) @@ -6,20 +6,12 @@ test omelette find-links = http://download.zope.org/distribution/ -unzip = true
I don't think zipped eggs are a win in any real scenario, except possibly the goofy file-count-limited GAE. I would strongly prefer that you revert this one change (you can override it in your own '~/.buildout/default.cfg').
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com
Tres Seaver wrote at 2008-8-28 15:22 -0400:
.... I don't think zipped eggs are a win in any real scenario, except possibly the goofy file-count-limited GAE. I would strongly prefer that you revert this one change (you can override it in your own '~/.buildout/default.cfg').
We have observed a drastic speedup (on both Windows and Linux) in import time (about 30 %) when we have put our complete (large) application (consisting among others of Zope 2, CMF, Archetypes) in a (single) zip file.
The probably reason:
Python's module lookup is very expensive. It makes about 5 pokes on each entry in "sys.path". These become "stat" for directory entries.
Looking into an in-memory zip content table is much faster than a filesystem "stat".
As the use of eggs drastically increases the number of entries in "sys.path", Python's imports are likely to get slower.
However, I am not sure whether our observations for a single large zip (in fact, we use two: one for our application, the other for Python's runtime library) is valid for the case of many small zipped eggs.
On Sat, Aug 30, 2008 at 2:03 AM, Dieter Maurer dieter@handshake.de wrote:
However, I am not sure whether our observations for a single large zip (in fact, we use two: one for our application, the other for Python's runtime library) is valid for the case of many small zipped eggs.
The single-large-zip and the many-small-zips are distinctly different; the zip-import support was intended to support the single-large-zip (or small-number-of-zips) cases. Having many small zips is not a win at all. (Don't recall if there's a real penalty over many unzipped directories.)
-Fred
On Aug 30, 2008, at 2:03 AM, Dieter Maurer wrote:
Tres Seaver wrote at 2008-8-28 15:22 -0400:
.... I don't think zipped eggs are a win in any real scenario, except possibly the goofy file-count-limited GAE. I would strongly prefer that you revert this one change (you can override it in your own '~/.buildout/default.cfg').
We have observed a drastic speedup (on both Windows and Linux) in import time (about 30 %) when we have put our complete (large) application (consisting among others of Zope 2, CMF, Archetypes) in a (single) zip file.
...
However, I am not sure whether our observations for a single large zip (in fact, we use two: one for our application, the other for Python's runtime library) is valid for the case of many small zipped eggs.
In fact, for a small application that I wanted to be able to run as a CGI, zipping several non-large eggs (such as zope.publisher, for example) made imports slower. It was faster to use unzipped eggs. This was on Linux.
Jim
-- Jim Fulton Zope Corporation
-
Dieter Maurer -
Fred Drake -
Jim Fulton -
Tres Seaver