[issue17573] add ElementTree XML processing benchmark to benchmark suite

Antoine Pitrou added the comment: I've committed the benchmarks after some changes: - smaller document to reduce runtimes - avoid measuring processing and serializing performance as part of the parsing benchmark - added an iterparse benchmark (iterparse can be important for e.g. XMPP implementa

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Roundup Robot added the comment: New changeset 723d7f134cf5 by Antoine Pitrou in branch 'default': Tweak etree benchmarks and add an etree_iterparse benchmark (followup to issue #17573). http://hg.python.org/benchmarks/rev/723d7f134cf5 -- ___ Python

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Roundup Robot added the comment: New changeset dbf5693d7013 by Antoine Pitrou in branch 'default': Issue #17573: add three elementtree benchmarks. Initial patch by Stefan Behnel. http://hg.python.org/benchmarks/rev/dbf5693d7013 -- nosy: +python-dev _

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Stefan Behnel added the comment: Ok, but an lxml benchmark is independent from this patch then. I updated it to only use cElementTree, with the additional "--etree-module" option and also a "--no-accelerator" option for advanced usage. Another thing I did is to split the actual benchmark code

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Antoine Pitrou added the comment: > I'm ok with the conditional import for ET, although I don't see a > reason to exclude it. Why not be able to compare the performance of > both implementations as well? There's a slowpickle benchmark, for > example. It made sense in 2.7 where both implementatio

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Stefan Behnel added the comment: I considered lxml.etree support more of a convenience feature, just for comparison. Given that it's a binary package that doesn't run reliably on other Python implementations apart of CPython, I don't think it's really interesting to make it part of the benchma

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Antoine Pitrou added the comment: Haven't looked at the patch in detail but a couple of things: - I don't think we need to benchmark the slow pure-Python ET, except when the fast version isn't present (basically, the main benchmark should try cET and then fallback on ET) - I'm ok with lxml be

[issue17573] add ElementTree XML processing benchmark to benchmark suite

Changes by Stefan Behnel : -- nosy: +brett.cannon, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue17573] add ElementTree XML processing benchmark to benchmark suite

New submission from Stefan Behnel: Here is an artificial but pretty broad ElementTree benchmark, testing the modules xml.etree.ElementTree, xml.etree.cElementTree and lxml.etree (if importable). Please add it to the benchmark suite. -- components: Benchmarks, XML files: add_et_benchmar