unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: jreeseue <jreeseue@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: Emacs 24.0.94.1 slow to load on OS X
Date: Mon, 5 Mar 2012 19:54:15 +0100	[thread overview]
Message-ID: <B37526E3-B7AC-44F1-B890-3E87AF6B8C46@Web.DE> (raw)
In-Reply-To: <33444508.post@talk.nabble.com>


Am 5.3.2012 um 17:08 schrieb jreeseue:

> 16:00@legolas:~$ time nslookup apple.com
> Server:		129.215.70.239
> Address:	129.215.70.239#53
> 
> Non-authoritative answer:
> Name:	apple.com
> Address: 17.149.160.49
> Name:	apple.com
> Address: 17.172.224.47
> 
> 
> real	0m1.018s
> user	0m0.009s
> sys	0m0.005s


No, that's probably not a network problem! The user and system times are as short as one would assume. The issue is with the real time used, from pressing RET until some text appeared on screen. This time is 1 sec too long, i.e., by a factor of 70.

Could be you're missing some GB of RAM and your Mac is constantly swapping. Little tools like MenuMeters or iStat menus could display in the  menu bar what's going on. In /private/var/vm the system stores the swap files. An easy check is to reboot your Mac, not opening any unnecessary applications, and then launching GNU Emacs.


Launching GNU Emacs your way is not the correct way. Check fast with 'emacs --help'! Instead of

	emacs .emacs -f "save-buffers-kill-terminal"

you could use

	emacs -q -l <some file with ELisp code> -f "save-buffers-kill-terminal"

or

	emacs -Q -l <some file with ELisp code> -f "save-buffers-kill-terminal"


--
Greetings
                                 <]
  Pete       o        __o         |__    o           recumbo
    ___o    /I       -\<,         |o \  -\),-%       ergo sum!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________




  reply	other threads:[~2012-03-05 18:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 17:36 Emacs 24.0.94.1 slow to load on OS X jreeseue
2012-03-03 18:31 ` Christopher Schmidt
2012-03-03 19:41   ` jreeseue
2012-03-03 19:33 ` Peter Dyballa
2012-03-03 19:42 ` Peter Dyballa
2012-03-03 19:46   ` jreeseue
2012-03-03 21:18     ` Peter Dyballa
2012-03-03 21:27       ` jreeseue
2012-03-03 21:52         ` Peter Dyballa
2012-03-03 22:19           ` jreeseue
2012-03-03 23:29             ` Peter Dyballa
2012-03-04 15:42               ` jreeseue
2012-03-05 16:08                 ` jreeseue
2012-03-05 18:54                   ` Peter Dyballa [this message]
2012-03-05 21:04                     ` jreeseue
2012-03-05 21:48                       ` Peter Dyballa
2012-03-05 22:03                         ` jreeseue

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=B37526E3-B7AC-44F1-B890-3E87AF6B8C46@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=Help-gnu-emacs@gnu.org \
    --cc=jreeseue@gmail.com \
    /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).