unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: HOWTO: lightning fast Emacs on Linux multicore
Date: Sun, 16 Nov 2014 21:34:36 +0100	[thread overview]
Message-ID: <87y4ranaub.fsf@debian.uxu> (raw)
In-Reply-To: 87h9xzh6xe.fsf@none.nowhere.com

jj.retorre@gmail.com (Jean-Jacques Rétorré) writes:

> I dont. I do the trick on my eeepcX101CH (Intel(R)
> Atom(TM) CPU N2600 @ 1.60GHz) and I dont see any
> significant difference.

There can be many reasons for this.

One can be - is Emacs already super-fast?

I have lots of configuration and extentions, and
though I've written it as cleverly as possible, I must
admit that the interactive feel of 'emacs -Q' is
faster, not much but I sense it. Just as I sense the
one-core solution is faster.

Try bring in a bunch of stuff in .emacs if you didn't
already - w3m, LaTeX, Gnus, everything you can think
of - and then compare that to 'emacs -Q'. If you don't
feel a difference, perhaps you already hit the roof.

As for your CPU I don't know what optimization,
parallelizations, and so on are at play at that level.
It is more like a electrical engineering thing
anyway :) But do enlighten us if you know.

-- 
underground experts united


  reply	other threads:[~2014-11-16 20:34 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 [this message]
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
     [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=87y4ranaub.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).