Maciej Fijalkowski, 18.02.2012 10:56: > On Sat, Feb 18, 2012 at 11:48 AM, Stefan Behnel wrote: >> Maciej Fijalkowski, 18.02.2012 10:35: >>> On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote: >>>> Given that XML processing is currently slower in PyPy than in CPython, I >>>> don't think that's all that bad. Users can still switch their imports to >>>> ElementTree if they only want to push XML out and I imagine that lxml would >>>> still be at least as fast as ElementTree under PyPy for the way in. >>> >>> Are you sure actually? >> >> I'm sure it's currently much slower, see here: >> >> http://blog.behnel.de/index.php?p=210 > > Can you please send me or post somewhere numbers? I'm fairly bad at > trying to deduce them from the graph (although that doesn't change > that the graph is very likely more readable).
I just noticed that I still had them lying around, so I'm pasting them here as tabified table. Columns: 274KB hamlet.xml, 3.4MB ot.xml, 25MB Slavic text, 4.5MB structure, 6.2MB structure PP MiniDOM (PyPy) 0,091 0,369 2,441 1,363 3,152 MiniDOM 0,152 0,672 6,193 5,935 8,705 lxml.etree 0,014 0,041 0,454 0,131 0,199 ElementTree (PyPy) 0,045 0,293 2,282 1,005 2,247 ElementTree 0,104 0,385 3,274 3,374 4,178 cElementTree 0,022 0,056 0,459 0,192 0,478 This was using PyPy 1.7, times are in seconds. As you can see, CPython is faster by a factor of 5-10 for the larger files. Stefan _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
