Robert Clipsham:
> This looks like the way to go for the benchmarks. When I've added all
> the tests people have sent me and added a reference C++ result I will
> put the results file under revision control with the rest of the source
> code and set up a script to generate graphs to show results
bearophile wrote:
Robert Clipsham, eventually your site may become like this page (it may be slow
to load, you may need to load it later too):
http://sbcl.boinkor.net/bench/
It's also useful to see how performance evolves across versions, like a brother
of bugzilla, to spot performance bugs.
Robert Clipsham, eventually your site may become like this page (it may be slow
to load, you may need to load it later too):
http://sbcl.boinkor.net/bench/
It's also useful to see how performance evolves across versions, like a brother
of bugzilla, to spot performance bugs.
Bye,
bearophile
Sorry, assuming a "tidy XML file" is silly. Better:
from xml.dom.minidom import parse
r = parse("results.xml").getElementsByTagName("results")
results = r[0].getElementsByTagName("result")
# print field names
fields = [n.localName for n in results[0].childNodes if n.nodeType !=
n.TEXT_NODE]
pri
naryl:
> I think this will suffice:
> $ sed 's/<[^>]*>//g; /^$/d' < data | sed 'N; N; N; N; N; N; s/\n/ /g'
A Python version a little more resilient to changes in that file:
from xml.dom.minidom import parse
results1 = parse("results.xml").getElementsByTagName("results")
results = results1[0].get
Robert Clipsham Wrote:
> bearophile wrote:
> > I don't like XML; a small txt table is so easy to process with three lines
> > of Python... :-)
> > (Json is fine too).
>
> If you would like to provide me with a script to convert the xml file to
> a text table, I'll happily run it and make it ava
bearophile wrote:
I don't like XML; a small txt table is so easy to process with three lines of
Python... :-)
(Json is fine too).
If you would like to provide me with a script to convert the xml file to
a text table, I'll happily run it and make it available to you. As it is
I'm too lazy to
Robert Clipsham:
>I've got a better idea. That page is automatically generated from an xml file,
>I'll just make that available instead.<
I don't like XML; a small txt table is so easy to process with three lines of
Python... :-)
(Json is fine too).
>I would probably have to exclude tests tha
bearophile wrote:
Robert Clipsham:
I have seen you have put all graphs in a page. This is probably better. When
you have 10-20 benchmarks you may need less thick bars.
You can add the raw timings, formatted into an ASCII table, a bit like this
(don't use an HTML table):
http://zi.fi/shootout/
Robert Clipsham:
I have seen you have put all graphs in a page. This is probably better. When
you have 10-20 benchmarks you may need less thick bars.
You can add the raw timings, formatted into an ASCII table, a bit like this
(don't use an HTML table):
http://zi.fi/shootout/rawresults.txt
There
bearophile wrote:
Robert Clipsham, the pages are indeed improved a lot. Thank you for your work.
Thanks, I'm glad you approve!
with all benchmarks limited to 256mb memory usage<
- Some benchmarks of the Shootout site will probably need more than 256 mb of
RAM.
None of the ones that I'm cu
Robert Clipsham, the pages are indeed improved a lot. Thank you for your work.
>with all benchmarks limited to 256mb memory usage<
- Some benchmarks of the Shootout site will probably need more than 256 mb of
RAM.
> The only request I believe I've missed (correct me if I'm wrong!) is a C
> or
12 matches
Mail list logo
