3 ms·
That is some horrible Common Lisp code. I have to try this out....
by mrottenkolber 12y ago
That is some horrible Common Lisp code. I have to try this out....
- mrottenkolber 12y agoNope sorry. I tried to fix this up a little but this is too convoluted for me to work with. Q1: Why do you need an adjustable array? Q2: Why do you need a structure with a single slot (node)? If you want to benchmark a piece of code, please write a nice version and then optimize it. How can I reason about a benchmark result if the code is not understandable?
- jawngee 12y agoYou should ask for a refund.
- mrottenkolber 12y agoI should, he used SBCL ticks (relative unit of time) as if they were milliseconds.
- wtf_is_up 12y agoMany others were able to send pull requests. What's you're issue?
- mrottenkolber 12y agoThe original code was badly written so that is was hard to understand the algorithm. I tried to rewrite it but it took longer than I had patience for. The snarky tone comes from the fact that people often post "benchmarks" including languages they can't program in resulting in a misrepresentation. E.g. Lisp jumped from the bottom to the center (as expected) of the benchmarks after somebody donated a sane implementation.
- lispm 12y agoI have improved it. https://github.com/logicchains/LPATHBench/blob/master/lisp.lisp https://github.com/logicchains/LPATHBench/blob/master/lisp.l...
- mrottenkolber 12y agoThank for the effort! Not sure how fleshed out the other implementations are but Lisp vs C now shows what I would have expected: * SBCL can produce impressive x86 code * It's ARM branch is pretty new, so it but 30% isn't too bad.