all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: 26.2; Strange slowness in some Info nodes
Date: Sat, 03 Aug 2019 09:48:10 +0300	[thread overview]
Message-ID: <831ry2g2xh.fsf@gnu.org> (raw)
In-Reply-To: <AxvjDw.r75CDrNNeVIh.fu4fyrxvqDb7MYqtYAlW@freemail.hu> (message from ndame on Fri, 2 Aug 2019 20:23:06 +0000 (GMT))

> Date: Fri, 2 Aug 2019 20:23:06 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> 
> Though I don't really get why repeated scrolling down is
> slow. I'd think the first one is slow when emacs finds the font
> for the character and then subsequent scroll downs should be
> quick, because then the font for the character is known. 

It is known, but that knowledge can be forgotten.

> It would be strange if the cached information were purged from
> memory right after it was found and emacs had to find the font
> again for the next scroll down.

It is purged during GC.  At the GC level, there's no information
available that could tell Emacs not to purge a font (the "right after"
part is perhaps evident to a human, but not to a program).  The basic
problem with this situation is that some very large fonts cause very
frequent GC, which evicts those large fonts, which then cause a lot of
consing when they are again loaded, which again causes GC soon, etc.



  reply	other threads:[~2019-08-03  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 20:23 26.2; Strange slowness in some Info nodes ndame
2019-08-03  6:48 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-02 19:49 Joe_Trivers
2019-08-02 19:24 ndame
2019-08-02 19:58 ` Eli Zaretskii
2019-08-02 15:37 ndame
2019-08-02 18:53 ` Eli Zaretskii

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=831ry2g2xh.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.