unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Cohen <acohen@ust.hk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: sorting in C
Date: Wed, 23 Feb 2022 21:52:20 +0800	[thread overview]
Message-ID: <878ru1heqz.fsf@ust.hk> (raw)
In-Reply-To: <83zgmhsp13.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Feb 2022 08:14:39 -0500")

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:

[...]

    EZ> The 5-fold slowdown is a pain, IMO.  Can we do better in the
    EZ> worst case?
    >> 
    >> Maybe, but probably not too much. That is the point of these
    >> hybrids---they improve on some cases and do worse on others. Its
    >> a win only if the real-world data favors the improved case.
    >> 
    >> I played around a bit more and lowering the length threshold to
    >> 40 might be a better compromise. I am working on a more thorough
    >> set of tests first.

    EZ> OK, thanks.  Let's see the improved numbers, and can you also
    EZ> show absolute times?  If they are short enough, the slowdown
    EZ> might not be significant, since if the data structure is larger,
    EZ> the slow method will not be used, right?  Or did I
    EZ> misunderstand?

Yes, I will show absolute numbers in the future (for reference, it is
microseconds). And you did not misunderstand---the "slow" method (which
is much faster for sorted lists :)) isn't used for longer cases.

[...]

    EZ> But for showing the performance, the license is not important,
    EZ> is it?

Right, that was sort of a joke---just buying time until I can produce
some nice looking data.  I'm trying to automate their production a bit
more.

    >> Shouldn't be that difficult (the algorithm itself is
    >> well-documented) but I'm not sure how much time I have to finish
    >> it.

    EZ> From my POV, take all the time you need.  Emacs 29 is far from a
    EZ> release.

Great, thanks.

-- 
Andrew Cohen



  reply	other threads:[~2022-02-23 13:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  2:52 sorting in C Andrew Cohen
2022-02-22 12:30 ` Eli Zaretskii
2022-02-22 12:54   ` Andrew Cohen
2022-02-22 13:11     ` Eli Zaretskii
2022-02-23  4:14   ` Andrew Cohen
2022-02-23 12:34     ` Eli Zaretskii
2022-02-23 12:53       ` Andrew Cohen
2022-02-23 13:14         ` Eli Zaretskii
2022-02-23 13:52           ` Andrew Cohen [this message]
2022-02-23 14:06           ` Andrew Cohen
2022-02-23 14:18             ` Eli Zaretskii
2022-02-26 23:54               ` Andrew Cohen
2022-02-27  2:27                 ` Andrew Cohen
2022-02-27  7:28                   ` Eli Zaretskii
2022-02-27  9:11                     ` Andrew Cohen
2022-02-27  9:29                       ` Eli Zaretskii
2022-02-27 10:42                         ` Andrew Cohen
2022-03-04  0:13                           ` Andrew Cohen
2022-03-04  7:05                             ` Eli Zaretskii
2022-02-23 13:19         ` Yuri Khan
2022-02-23 14:12           ` Andrew Cohen
2022-02-22 13:12 ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ru1heqz.fsf@ust.hk \
    --to=acohen@ust.hk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).