From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: HOWTO: lightning fast Emacs on Linux multicore
Date: Sun, 16 Nov 2014 22:25:13 +0200 [thread overview]
Message-ID: <83k32udhau.fsf@gnu.org> (raw)
In-Reply-To: <20141116123211220580626@bob.proulx.com>
> Date: Sun, 16 Nov 2014 12:49:52 -0700
> From: Bob Proulx <bob@proulx.com>
>
> > Now, Emacs has a core to itself and should run much
> > faster, at least for normal usage.
>
> I am happy if you are happy with the above. However I recommend not
> doing this.
Seconded.
> I think it is better to allow the kernel to optimize process
> scheduling itself. As I said, if you are happy then I am happy for
> you. But I wouldn't recommend this to others since it will generally
> slow down the system.
In general, one should keep out of the scheduler's way, unless they
have a VERY good reason. Such reasons can only pop up when you need
to run some software with hard real-time deadlines (and even then
there are better ways). Any other reason is by definition to good
enough.
next prev parent reply other threads:[~2014-11-16 20:25 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 [this message]
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k32udhau.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.
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.