From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Making IMAP fasterer
Date: Wed, 14 Jun 2017 23:57:13 -0700 [thread overview]
Message-ID: <m2wp8dkaba.fsf@boostpro.com> (raw)
In-Reply-To: <87wpkvw70r.fsf@math.uh.edu>
on Sat Jul 09 2016, Jaspn Tibbitts <tibbs-AT-math.uh.edu> wrote:
> I'm on vacation and instead of my usual method of ssh-ing into my work
> machine and running emacs in a screen session, I thought I'd try setting
> up gnus locally. And it works, but it's pretty slow. I'm running
> Fedora 24, with emacs 25.0.94 the version of gnus which comes with it
> (5.13).
>
> I think that the issue is that the path to my IMAP server has a bit of
> latency, which isn't surprising considering I'm on a Norwegian island
> not far from the arctic circle. I have always had gnus-asynchronous
> set, and I remember in the past it used to flash messages about the
> articles it was prefetching. I haven't seen that in a while, and it
> doesn't look like gnus is doing any article prefetching. So selecting
> an article takes a couple of seconds while it does a bunch of round
> trips.
>
> In addition, gnus-group-get-new-news always tells me "nnimap read NNNk
> from imap.math.uh.edu (initial sync of 4 groups; please wait)" while it
> fetches about 400k in total. This takes about ten seconds every time i
> hit 'g', which I'm trying to condition myself not to do.
>
> So, does anyone have any tips for making it run a bit smoother?
I use http://onmsg.github.io
--
-Dave
prev parent reply other threads:[~2017-06-15 6:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 8:27 Jaspn Tibbitts
2016-07-09 9:03 ` Steinar Bang
2016-07-09 9:10 ` Steinar Bang
2016-07-09 10:58 ` Jaspn Tibbitts
2016-07-09 9:32 ` Eric Abrahamsen
2016-07-09 10:52 ` Jaspn Tibbitts
2016-07-09 12:14 ` Eric Abrahamsen
2016-07-09 13:07 ` Steinar Bang
2016-07-21 6:28 ` Steinar Bang
2016-07-21 21:02 ` Jason Tibbitts
2016-07-21 21:06 ` Steinar Bang
2017-06-15 6:57 ` Dave Abrahams [this message]
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=m2wp8dkaba.fsf@boostpro.com \
--to=dave@boostpro.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).