From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: Asynchroneous image retrieval in HTML rendering
Date: Mon, 02 May 2011 09:52:17 +0200 [thread overview]
Message-ID: <87liyp35fy.fsf@gmail.com> (raw)
In-Reply-To: <m3aaf6ig1d.fsf@quimbies.gnus.org>
01/05/11 17:42, Lars Magne Ingebrigtsen
> Antoine Levitt <antoine.levitt@gmail.com> writes:
>
>>> I think the fix here might be to introduce a new variable
>>> `url-asynchronous-dns-lookup' (or something), and then have shr bind it
>>> to make url.el more asynchronous. The pauses we experience today when
>>> trying to do asynchronous URL retrieval aren't acceptable. Especially
>>> if a domain is down or semi-down -- reading the articles becomes almost
>>> impossible.
>
> Oopsie. Actually, the image retrieval in Emacs 24 was extremely
> synchronous. Due to changes in `open-network-stream', the :nowait flag
> was no longer passed on, so all connections were established
> synchronously, even if url.el tried to do it asynchronously.
>
> I've now fixed this and pushed the fix to Emacs 24.
That doesn't change much for my test cases, so I guess the DNS lookup is
indeed the bottleneck.
>
>> Why is DNS even synchroneous in the first place? I'd expect
>> "asynchroneous" to mean that both DNS lookup and data transfer are
>> non-blocking.
>
> Emacs uses the built-in resolver (from C), and it does it in the main
> Emacs thread. So whenever you resolve something in Emacs, *everything*
> in Emacs stops.
>
> I've written the dns.el resolver in Emacs Lisp, but, of course, it's not
> as sturdy as the libc one. (And only works on Linux.) A better fix
> would be to write a C-level resolver that forks its own thread, does the
> resolving, and then does a callback.
Damn emacs monothread model ;)
next prev parent reply other threads:[~2011-05-02 7:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 22:18 Antoine Levitt
2011-04-28 20:03 ` Antoine Levitt
2011-04-29 9:04 ` Julien Danjou
2011-04-29 9:18 ` Antoine Levitt
2011-04-29 10:01 ` Julien Danjou
2011-04-29 20:34 ` Antoine Levitt
2011-05-01 15:13 ` Lars Magne Ingebrigtsen
2011-05-01 15:23 ` Antoine Levitt
2011-05-01 15:42 ` Lars Magne Ingebrigtsen
2011-05-01 16:06 ` Lars Magne Ingebrigtsen
2011-05-01 16:34 ` Adam Sjøgren
2011-05-01 16:45 ` Lars Magne Ingebrigtsen
2011-05-01 17:15 ` Antoine Levitt
2011-05-02 7:52 ` Antoine Levitt [this message]
2011-05-02 14:30 ` Lars Magne Ingebrigtsen
2011-05-02 14:53 ` Antoine Levitt
2011-05-02 15:17 ` Lars Magne Ingebrigtsen
2011-05-02 17:08 ` Lars Magne Ingebrigtsen
2011-05-02 17:24 ` Antoine Levitt
2011-05-02 17:40 ` Lars Magne Ingebrigtsen
2011-05-02 21:52 ` Antoine Levitt
2011-05-04 18:40 ` Simon Josefsson
2011-05-30 20:55 ` Lars Magne Ingebrigtsen
2011-05-05 8:25 ` Julien Danjou
2011-05-30 20:56 ` Lars Magne Ingebrigtsen
2011-05-05 10:48 ` Ted Zlatanov
2011-05-05 10:58 ` Julien Danjou
2011-05-05 11:17 ` Antoine Levitt
2011-05-05 13:51 ` Ted Zlatanov
2011-05-05 14:01 ` David Engster
2011-05-05 14:07 ` Julien Danjou
2011-05-05 15:05 ` Lars Magne Ingebrigtsen
2011-05-05 19:49 ` David Engster
2011-05-05 20:07 ` Lars Magne Ingebrigtsen
2011-05-05 14:25 ` David Engster
2011-05-05 14:34 ` Antoine Levitt
2011-05-05 14:59 ` David Engster
2011-05-05 15:00 ` David Engster
2011-05-02 17:53 ` Lars Magne Ingebrigtsen
2011-05-02 18:18 ` Lars Magne Ingebrigtsen
2011-05-02 17:12 ` Ted Zlatanov
2011-05-02 17:20 ` Lars Magne Ingebrigtsen
2011-05-02 21:18 ` Steinar Bang
2011-05-02 22:40 ` Lars Magne Ingebrigtsen
2011-05-03 14:09 ` Ted Zlatanov
2011-05-03 18:48 ` Steinar Bang
2011-05-02 21:15 ` Steinar Bang
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=87liyp35fy.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=ding@gnus.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 NNTP newsgroup(s).