unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: HOWTO: lightning fast Emacs on Linux multicore
Date: Sun, 16 Nov 2014 03:55:29 +0100	[thread overview]
Message-ID: <8761efyhum.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: 871tpdl29g.fsf@debian.uxu

Emanuel Berg <embe8573@student.uu.se> writes:

> A couple of months ago I got a multicore computer.
> Better yet, it is a dualcore :)

If you want to have fun, perhaps implementing a few emacs lisp library
functions in parallel (multi-threaded), could speed things up.

You'd have to find out what operations (particularly on big buffers) are
slow and parallelizable.

For example, replace-string could split its start/end range, (check the
cuts for occurences) and then process each range in parallel.

Similarly, replace-regexp and fontifying which is often thought to be
slow, could benefit (taking the same precautions around the cuts).

A lot of code that use iterative search (re-search-forward) could
probably be upgraded, using a function (such as re-all-matches) that
would perform the search in parallel on the different ranges.


-- 
__Pascal Bourguignon__                 http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk


  parent reply	other threads:[~2014-11-16  2:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-08 23:07 HOWTO: lightning fast Emacs on Linux multicore Emanuel Berg
2014-11-10  2:05 ` Marcin Borkowski
     [not found] ` <mailman.13356.1415585130.1147.help-gnu-emacs@gnu.org>
2014-11-15 19:26   ` Emanuel Berg
2014-11-16  1:13     ` York Zhao
     [not found]     ` <mailman.13774.1416100398.1147.help-gnu-emacs@gnu.org>
2014-11-16  7:46       ` Emanuel Berg
2014-11-16  7:57         ` Jean-Jacques Rétorré
2014-11-16  8:07           ` Emanuel Berg
2014-11-16  8:43             ` Jean-Jacques Rétorré
2014-11-16 20:34               ` Emanuel Berg
2014-11-16  2:55 ` Pascal J. Bourguignon [this message]
2014-11-16  7:41   ` Emanuel Berg
2014-11-16 19:49 ` Bob Proulx
2014-11-16 20:25   ` Eli Zaretskii
     [not found] ` <mailman.13827.1416167406.1147.help-gnu-emacs@gnu.org>
2014-11-16 21:04   ` Emanuel Berg
2014-11-16 21:39     ` Bob Proulx
2014-11-17  3:42       ` Eli Zaretskii
     [not found]     ` <mailman.13834.1416173992.1147.help-gnu-emacs@gnu.org>
2014-11-16 21:58       ` Emanuel Berg

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=8761efyhum.fsf@kuiper.lan.informatimago.com \
    --to=pjb@informatimago.com \
    --cc=help-gnu-emacs@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.
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).