From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs Slowdown
Date: Tue, 10 Mar 2015 12:37:15 +0000 [thread overview]
Message-ID: <87wq2pf2pw.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <83pp8i5ep9.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 9 Mar 2015 18:16:18 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: phillip.lord@newcastle.ac.uk (Phillip Lord)
>> Date: Mon, 09 Mar 2015 11:48:47 +0000
>>
>> I am suffering a rather disasterous slowdown in my emacs. It feels like
>> a memory leak, as my emacs gets slower over time. It mostly seems to be
>> affected auctex, where there is considerable lag in cursor movement to
>> the point that typing becomes difficult.
>
> For starters, customize garbage-collection-messages to a non-nil
> value, and see if Emacs announces GC while cursor movement is
> sluggish.
Ah, yes, forgotten that one.
> If you want to test the hypothesis of a memory leak, it's easier to
> look at your Emacs process's virtual memory size, either in 'top' or
> in "M-x proced". Take a few snapshots of the value and try to
> correlate that with the values reported by 'garbage-collect'. If
> those values stay approximately stable, or go down, but the VSS of the
> process goes up, you can suspect a memory leak; otherwise the problem
> is elsewhere.
>
> (Personally, I wouldn't pursue the memory leak avenue first,
> especially if this is an official release, not a development version
> of Emacs: I think other possible reasons are much more probable. But
> that's me.)
I've been using both using both releases and development. I'd agree,
I've not found many memory leaks in my time.
>> which is an awful lot of functions to be called on every keypress. I
>> realise that I may have gone a bit overboard here, especially as five of
>> those functions are mine!
>
> The question is: what do those hook do, on average? If they are very
> lightweight (profile them to see if they are), then this isn't your
> villain.
>
> Also, try removing most of the hooks when you see sluggish operation,
> and see if that brings any significant speedup; if not, these aren't
> what you are looking for.
Saw Stefan's post and think these are a red-herring also.
Phil
next prev parent reply other threads:[~2015-03-10 12:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 11:48 Emacs Slowdown Phillip Lord
2015-03-09 16:16 ` Eli Zaretskii
2015-03-09 21:50 ` Stefan Monnier
2015-03-10 12:37 ` Phillip Lord [this message]
2015-03-10 19:00 ` Eli Zaretskii
2015-03-09 21:59 ` Stefan Monnier
2015-03-10 12:39 ` Phillip Lord
2015-03-10 13:22 ` Stefan Monnier
2015-03-12 11:36 ` Phillip Lord
2015-03-16 11:41 ` Phillip Lord
2015-03-16 12:36 ` Stefan Monnier
2015-03-16 16:51 ` Phillip Lord
2015-03-18 12:23 ` Phillip Lord
2015-03-18 12:44 ` Stefan Monnier
2015-03-18 14:13 ` Phillip Lord
2015-03-18 14:53 ` Stefan Monnier
2015-03-18 16:34 ` Phillip Lord
2015-03-18 16:32 ` Eli Zaretskii
2015-03-18 17:04 ` Phillip Lord
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=87wq2pf2pw.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=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).