From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 57079@debbugs.gnu.org
Subject: bug#57079: 29.0.50; Performance of seq-uniq is not very good
Date: Tue, 09 Aug 2022 19:47:33 +0300 [thread overview]
Message-ID: <83tu6ltlcq.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=TQ58SaA3RGt3TerY4nB7n5nr+H3oD4JUqJw1CkUsSzQ@mail.gmail.com> (message from Stefan Kangas on Tue, 9 Aug 2022 09:11:07 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 9 Aug 2022 09:11:07 -0700
>
> Severity: minor
>
> `seq-uniq' is not very performant compared to `-uniq' (from dash.el) and
> even slower compared to the recently removed `gnus-delete-duplicates':
>
> (benchmark-run 10000 (seq-uniq '(a c b c c a d)))
> => (0.355001481 1 0.2518970439999748)
>
> (benchmark-run 10000 (-uniq '(a c b c c a d)))
> => (0.006599549 0 0.0)
>
> (benchmark-run 10000 (gnus-delete-duplicates '(a c b c c a d)))
> => (0.0034537929999999997 0 0.0)
>
> Could we improve the performance of `seq-uniq' for lists?
What's wrong with using delete-dups for your cases above?
next prev parent reply other threads:[~2022-08-09 16:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 16:11 bug#57079: 29.0.50; Performance of seq-uniq is not very good Stefan Kangas
2022-08-09 16:47 ` Eli Zaretskii [this message]
2022-08-09 16:57 ` Lars Ingebrigtsen
2022-08-09 17:07 ` Eli Zaretskii
2022-08-09 17:21 ` Lars Ingebrigtsen
2022-08-09 17:45 ` Stefan Kangas
2022-08-09 17:18 ` Eli Zaretskii
2022-08-09 17:23 ` Lars Ingebrigtsen
2022-08-09 17:36 ` Eli Zaretskii
2022-08-09 17:50 ` Eli Zaretskii
2022-08-09 17:52 ` Lars Ingebrigtsen
2022-08-09 17:59 ` Eli Zaretskii
2022-08-09 18:03 ` Lars Ingebrigtsen
2022-08-09 18:16 ` Eli Zaretskii
2022-08-09 19:35 ` Juri Linkov
2022-08-12 13:16 ` Lars Ingebrigtsen
2022-08-12 23:59 ` Michael Heerdegen
2022-08-13 11:50 ` Lars Ingebrigtsen
2022-08-13 20:24 ` Michael Heerdegen
2022-08-15 6:39 ` Lars Ingebrigtsen
2022-08-15 23:37 ` Michael Heerdegen
2022-08-17 11:01 ` Lars Ingebrigtsen
2022-08-20 3:17 ` Michael Heerdegen
2022-08-20 9:19 ` Lars Ingebrigtsen
2022-08-20 15:13 ` Drew Adams
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=83tu6ltlcq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57079@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.