On 6 May 2012 04:27, Vlad K. <v...@haronmedia.com> 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

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-discuss+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to