unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Make emacs-eww render asynchronously
Date: Tue, 19 Mar 2019 15:13:35 -0400	[thread overview]
Message-ID: <jwvr2b2u1mn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 9001.50727700151$1553019555@news.gmane.org

> In case anyone is reading this and thinking "get off your heirloom VAX
> grandpa, here is a nickel, buy a better computer," there is no reason
> for computers with gigahertz-plus CPUs and a gigabyte of memory to end
> up in the landfill, even if they are 10+ years old.  And work on
> performance issues caused by sloppy code and bad algorithms/data
> structures will benefit all GNU Emacs users.

My main laptop is a Thinkpad T61, my office desktop is a 2006 mac-mini,
so yes, I fully agree.

>> The emacs-w3m fetches the page asynchronously, but the rendering process
>> will freeze Emacs for a long time.
> Yes, this is an actual problem.  Óscar Fuentes probably does not
> notice it because he must have a fast computer - if you are hacking
> elisp code it is a good idea to do it on old slow hardware.

One of the reasons why we can still use 10+ year old computers is
because even the fanciest newest CPUs aren't *that* much faster (on
single-threaded code, as is the case here) thanks to the end of Dennard
scaling, so if it's "less than a second" on Óscar's computer there's
a good chance that it should be much less than "a long time" on the
OP's machine.

IOW there's probably some other difference than the hardware at play here.


        Stefan




  reply	other threads:[~2019-03-19 19:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  4:48 Make emacs-eww render asynchronously YUE Daian
2019-03-19 15:11 ` Óscar Fuentes
2019-03-19 18:10 ` Vladimir Sedach
2019-03-19 19:13   ` Stefan Monnier [this message]
2019-03-19 19:26   ` Óscar Fuentes
2019-03-19 19:04 ` Stefan Monnier
2019-03-19 19:31 ` Óscar Fuentes
     [not found] ` <87zhpqn3af.fsf@exinda.orion.oneofus.la.>
2019-03-19 19:35   ` Eli Zaretskii
2019-03-20  7:03     ` Vladimir Sedach
2019-03-20 14:04       ` Stefan Monnier
     [not found] ` <5c9132a1.1c69fb81.b855.49c7SMTPIN_ADDED_BROKEN@mx.google.com>
2019-03-20  4:31   ` YUE Daian

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=jwvr2b2u1mn.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).