From: "Daniel Bünzli" <daniel.buenzli@epfl.ch>
To: Stefano Zacchiroli <zack@bononia.it>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ANNOUNCE: Xmlm
Date: Tue, 27 Feb 2007 12:29:49 +0100 [thread overview]
Message-ID: <21AB6F18-E8C2-4D00-8067-F11D8DCD00FD@epfl.ch> (raw)
In-Reply-To: <20070227082805.GA4631@takhisis.invalid>
Le 27 févr. 07 à 09:28, Stefano Zacchiroli a écrit :
> What about the performance?
I don't know, I didn't invest a lot of time in profiling, maybe it
can be improved.
But if you want an unscientific benchmark here you have :
I compare the two programs xmllint (which comes on my system) and
xmltrip (compiled without any special option) respectively
distributed with libxml and xmlm. Note xmllint is a C program so we
are not comparing to libxml's ocaml interface. Besides I have no idea
how xmllint is written and what it does internally, maybe it does
more than xmlm does, so we may well be comparing the uncomparable.
The files are <http://www.ximpleware.com/xmls.zip>, uncompressed this
is 144 mb of xml files.
On macos 10.4.8, G4 1Ghz, 512mo ram.
Parse only, without building the tree.
> > time ./xmltrip.opt -p -ename ~/tmp/xmls/*.xml
>
> real 0m53.567s
> user 0m51.562s
> sys 0m1.043s
>
> > time xmllint --noent --nocdata --noout --nonet --stream ~/tmp/
> xmls/*.xml
>
> real 0m25.264s
> user 0m24.314s
> sys 0m0.725s
Parse only, building an in-memory tree.
> > time ./xmltrip.opt -t -p -ename ~/tmp/xmls/*.xml
>
> real 2m2.099s
> user 1m44.821s
> sys 0m8.215s
>
> > time xmllint --noblanks --noent --nocdata --noout --nonet ~/tmp/
> xmls/*.xml
> real 1m4.590s
> user 0m47.561s
> sys 0m3.193s
Best,
Daniel
prev parent reply other threads:[~2007-02-27 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 1:16 Daniel Bünzli
2007-02-27 8:28 ` [Caml-list] " Stefano Zacchiroli
2007-02-27 11:29 ` Daniel Bünzli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21AB6F18-E8C2-4D00-8067-F11D8DCD00FD@epfl.ch \
--to=daniel.buenzli@epfl.ch \
--cc=caml-list@yquem.inria.fr \
--cc=zack@bononia.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox