|
From: | Tino Calancha |
Subject: | bug#27560: 26.0.50; seq-uniq is slow |
Date: | Mon, 3 Jul 2017 23:19:27 +0900 (JST) |
User-agent: | Alpine 2.20 (DEB 67 2015-01-07) |
On Mon, 3 Jul 2017, Nicolas Petton wrote:
Nicolas Petton <nicolas@petton.fr> writes:Indeed, I will run some benchmarks as well. In your benchmarks, cl-lib is still much faster than seq-uniq, even if it's not as impressive as Oleh's benchmark.It looks like I read the benchmark results wrong :)seq-uniq seems to be much faster than in 2015, while its definition basically hasn't changed. I won't investigate much further as I'm happy with then benchmark results.
I am quite amazed with the 27 garbage collections that Oleh found:
(benchmark-run (seq-uniq cands 'equal)) (5.270219822 27 2.396615401000002)
I might get occasionally 1 gc, tipically 0: 27 demands a double checking. Tino
[Prev in Thread] | Current Thread | [Next in Thread] |