unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Skarda <dan.skarda@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Speed improvements to ido.el
Date: Thu, 22 Nov 2012 10:36:01 +0100	[thread overview]
Message-ID: <CAAfMPgCMaxDh4jdAUjeODCkEGmUFZBZcXnCFF+jScqSLZHh2iw@mail.gmail.com> (raw)
In-Reply-To: <87fw438w46.fsf@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

Hi Dmitry,

thanks for the suggestions. I will prepare some benchmarks using new Emacs
and send the results.
I already did some statistics with elp during development, but I suspect
that the numbers are not precise.

I am curious which improvements will be the fastest :)

Regards,
Dan

On Wed, Nov 21, 2012 at 4:37 AM, Dmitry Gutov <dgutov@yandex.ru> wrote:

> Daniel Skarda <dan.skarda@gmail.com> writes:
>
> Hey Daniel,
>
> Like Leo said, please provide some numbers.
>
> A comparison to the current trunk would be best, since it contains an
> additional optimization compared to the emacs-24 branch.
>
> Here my test setup from the relevant discussion:
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12796#47
>
> --Dmitry
>
> > I like to use ido mode for everything, including very large lists (like
> M-x or
> > info). Unfortunately ido is not suitable for such lists. On my old
> notebook,
> > performance is not amazing, so I took the challenge and spend some time
> with
> > profiler.
> >
> > I improved the performance in several steps:
> >
> > - inlined several functions
> > - disabled ido-case-fold for some completions (eg commands)
> > - prunning collections based on character bitmaps
> > - caching character bitmaps during completion or for same completions
> > - caching intermediate completion lists when adding new characters
> >
> > You can view my changes on github:
> >
> > - https://github.com/orfelyus/ido-speed-hack
> > - https://github.com/orfelyus/ido-mode-el
> >
> > - (and optionally) https://github.com/orfelyus/ido-better-flex
> >
> > ido-speed-hack includes large changes (bitmaps) while ido-mode-el
> includes minor
> > changes to ido.el
> >
> > The changes made huge speed improvements on my notebook and ido does not
> feel
> > sluggish even with very large lists.
> >
> > Could you please test my improvements? I would appreciate any feedback.
> > Dan
> >
> > ps: I am not subscribed to the mailing list, please keep me in Cc
>

[-- Attachment #2: Type: text/html, Size: 2992 bytes --]

  reply	other threads:[~2012-11-22  9:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 18:25 Speed improvements to ido.el Daniel Skarda
2012-11-21  3:20 ` Leo
2012-11-21  3:37 ` Dmitry Gutov
2012-11-22  9:36   ` Daniel Skarda [this message]
2012-11-30 13:42     ` Daniel Skarda
2012-12-01  0:40       ` Dmitry Gutov

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=CAAfMPgCMaxDh4jdAUjeODCkEGmUFZBZcXnCFF+jScqSLZHh2iw@mail.gmail.com \
    --to=dan.skarda@gmail.com \
    --cc=dgutov@yandex.ru \
    --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).