Python Memory Manager
Jeff Schwab
jeff at schwabcenter.com
Mon Feb 18 17:28:55 EST 2008
MartinRinehart at gmail.com wrote:
>
> Paul Rubin wrote:
>> The problem here is with a high allocation rate, you have to GC a lot
>> more often, which typically involves copying live data.
>
> This is last century's issue. Copying data, RAM to RAM, is nearly free
> using the Intel architecture.
What's "the Intel architecture?" Do you mean the x86_64 architecture
that was actually developed by AMD, or x86 for x > some number, or do
you actually mean IA64?
>
> This short article, http://www.martinrinehart.com/articles/repz.html
> explains why.
>
> I'd use one int per clock as a rule of thumb for the current copy rate
> in a single-core CPU.
More information about the Python-list
mailing list