On 05/06/2012 08:55 AM, Malthe Borch wrote:
On 6 May 2012 04:27, Vlad K.<[email protected]> wrote:
I've got about 20 XML file formats to construct, each produced by its own
(pluggable) module because each defines its own format etc... Switching to a
file-based partial generation would mean a massive rewrite. I guess this is
one of the situations where "preemptive optimization is evil" bit me because
I _was_ concerned with performance when I started building the system.
Admittedly at that point I wasn't aware of the Pythons memory retention
"policy".
If you want to explore the issue a bit further, you can get another
data point and possibly a solution by compiling Python without its own
memory manager. In this case, release really should mean release, or
there's something wrong with your operating system :-).
\malthe
This sounds like something I wouldn't want to do in production unless
I'm 100% sure I know what I'm doing, and I'm not :)
I didn't know it was possible and is definitely something I should toy
with outside of production to see how it works. Thanks for the suggestion.
.oO V Oo.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
