Gnus development mailing list
 help / color / mirror / Atom feed
From: Sebastian Krause <krause@sdbk.de>
Cc: Simon Josefsson <jas@extundo.com>
Subject: Re: Checking new mail very slow with current CVS
Date: Wed, 09 Jan 2002 18:08:53 +0100	[thread overview]
Message-ID: <krause.87pu4jlae2.fsf@sdbk.de> (raw)
In-Reply-To: <iluitask79l.fsf@extundo.com> (Simon Josefsson's message of "Thu, 27 Dec 2001 16:33:10 +0100")

Simon Josefsson <jas@extundo.com> writes:
> Russ Allbery <rra@stanford.edu> writes:
>> However, the speed difference is still very noticeable.  What follows is
>> two elp-results from instrumenting both "gnus" and "nn"; the first is from
>> Oort (CVS pull as of a few days ago) and the second is from 5.8.7.
>
> Thank you.  FWIW, I can reproduce this.  Gnus 5.9.0 from Emacs 21 is
> faster than Oort Gnus 0.0.4 (8 seconds vs 12 seconds for me).  The
> following speed things up, but I don't think everything can be blamed
> on this.  Does it have any effect for you?

I had the same problem with the current CVS and your patch solved my
problem that Gnus takes a long time when I hit 'g' in the Group
buffer. Could anyone please patch the current CVS with Simon's
following patch, it seems to me that this solution isn't in the CVS
yet, because i still had the problem with the current Oort Gnus from
a few hours ago.

> --- nntp.el.~6.15.~	Tue Oct 30 18:47:08 2001
> +++ nntp.el	Thu Dec 27 16:31:50 2001
> @@ -396,15 +396,15 @@
>  			    nntp-address nntp-port-number nntp-server-buffer
>  			    wait-for nnheader-callback-function)
>        ;; If nothing to wait for, still remove possibly echo'ed commands
> -      (unless wait-for
> -	(nntp-accept-response)
> -	(save-excursion
> -	  (set-buffer buffer)
> -	  (goto-char pos)
> -	  (if (looking-at (regexp-quote command))
> -	      (delete-region pos (progn (forward-line 1) (gnus-point-at-bol))))
> +;      (unless wait-for
> +;	(nntp-accept-response)
> +;	(save-excursion
> +;	  (set-buffer buffer)
> +;	  (goto-char pos)
> +;	  (if (looking-at (regexp-quote command))
> +;	      (delete-region pos (progn (forward-line 1) (gnus-point-at-bol))))
> +;	  )))
>  	  )))
> -    ))
>
>  (defun nntp-send-command-nodelete (wait-for &rest strings)
>    "Send STRINGS to server and wait until WAIT-FOR returns."

Sebastian



  reply	other threads:[~2002-01-09 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-25  6:49 Russ Allbery
2001-12-25 13:36 ` Simon Josefsson
2001-12-25 22:07   ` Russ Allbery
2001-12-25 22:15     ` Russ Allbery
2001-12-25 23:11     ` Simon Josefsson
2001-12-26  0:41       ` Russ Allbery
2001-12-26 13:56         ` Simon Josefsson
2001-12-26 21:32           ` Russ Allbery
2001-12-26 21:55             ` Simon Josefsson
2001-12-26 23:26             ` Steve Youngs
2002-01-03 18:59             ` Jan Vroonhof
2002-01-03 19:22               ` Simon Josefsson
2002-01-04 13:00                 ` Jan Vroonhof
2002-01-04 15:19                   ` Jan Vroonhof
2002-01-05  6:02                   ` Russ Allbery
2001-12-27 10:04           ` Russ Allbery
2001-12-27 15:33             ` Simon Josefsson
2002-01-09 17:08               ` Sebastian Krause [this message]
2002-01-09 17:42                 ` Simon Josefsson

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=krause.87pu4jlae2.fsf@sdbk.de \
    --to=krause@sdbk.de \
    --cc=jas@extundo.com \
    /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).