Reid Kleckner <rnk <at> mit.edu> writes:
> 
> > This is positively humongous. Is there any way to shrink these numbers
> > dramatically (I'm talking about the release builds)? Large executables or
> > libraries may make people anxious about the interpreter's memory
> > efficiency; and they will be a nuisance in many situations (think making
> > standalone app bundles using py2exe or py2app).
> 
> When we link against LLVM as a shared library, LLVM will still all be
> loaded into memory, but it will be shared between all python
> processes.

How large is the LLVM shared library? One surprising data point is that the
binary is much larger than some of the memory footprint measurements given in
the PEP. Do those measurements ignore some of the space taken by
unladen-swallow? Or is it rather that the binary contains lots of never used
code?

Regards

Antoine.


_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to