unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: HOWTO: lightning fast Emacs on Linux multicore
Date: Mon, 17 Nov 2014 05:42:32 +0200	[thread overview]
Message-ID: <83h9xycx1z.fsf@gnu.org> (raw)
In-Reply-To: <20141116142736830858969@bob.proulx.com>

> Date: Sun, 16 Nov 2014 14:39:40 -0700
> From: Bob Proulx <bob@proulx.com>
> 
> But even when working almost entirely within emacs the emacs process
> itself will depending upon what you are doing eventually spawn
> children processes.

Right.  Moreover, Emacs nowadays uses more than one thread, at least
when built with GTK.  And the OS itself uses more than one thread when
it services system requests on Emacs's behalf.

So running one program certainly doesn't mean one execution unit is
enough, or optimal.



  reply	other threads:[~2014-11-17  3:42 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
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 [this message]
     [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=83h9xycx1z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).