* Entering nnimap group got much slower with 5.10
@ 2003-05-09 0:14 Gleb Arshinov
2003-05-09 9:53 ` Simon Josefsson
0 siblings, 1 reply; 19+ messages in thread
From: Gleb Arshinov @ 2003-05-09 0:14 UTC (permalink / raw)
Just upgraded to 5.10.2 from Oort 0.08. I erased .newsrc.eld and ~/News
to do a clean upgrade.
Entering a large (~1200 messages, most with ! mark) IMAP newsgroup
now takes a very long time (elp results included below). Most of this
time modleline indicates "Fetching headers", which is unexpected (they
should be all cached). If I (setq gnus-agent-mode nil), I get good
performance (~1s to enter), but then I trigger old "nnimap eats all
email" bug.
What should I do to get to the bottom of this?
Gleb
Gnus v5.10.2 XEmacs 21.4 (patch 5) "Civil Service" [Lucid] (i686-pc-linux)
Function Name Call Count Elapsed Time Average Time
============================================================= ========== ============ ============
gnus-retrieve-headers 2 23.366241 11.6831205
gnus-topic-select-group 1 14.476583 14.476583
gnus-group-select-group 1 14.476504 14.476504
gnus-group-read-group 1 14.476493 14.476493
gnus-summary-read-group 1 14.476417 14.476417
gnus-summary-read-group-1 1 14.476404 14.476404
gnus-select-newsgroup 1 11.898781 11.898781
gnus-fetch-headers 1 11.823922 11.823922
gnus-cache-retrieve-headers 1 11.683221 11.683221
gnus-summary-prepare 1 2.536048 2.536048
gnus-summary-prepare-threads 1 2.323965 2.323965
gnus-correct-length 3580 0.5000589999 0.0001396812
gnus-put-text-property 2390 0.2509660000 0.0001050066
gnus-xmas-format 1201 0.2418010000 0.0002013330
gnus-sort-threads 1 0.189166 0.189166
gnus-sort-threads-1 29 0.189063 0.0065194137
gnus-char-width 33021 0.1819250000 5.509...e-06
gnus-run-hooks 1201 0.1551760000 0.0001292056
gnus-get-newsgroup-headers-xover 1 0.140041 0.140041
gnus-summary-highlight-line 1191 0.1301559999 0.0001092829
gnus-xmas-put-text-property 2390 0.0900830000 3.769...e-05
gnus-summary-from-or-to-or-newsgroups 1193 0.0690499999 5.787...e-05
gnus-request-group 1 0.067098 0.067098
gnus-put-text-property-excluding-characters-with-faces 1192 0.0636669999 5.341...e-05
gnus-extract-address-components 1193 0.046636 3.909...e-05
gnus-gather-threads-by-subject 1 0.018247 0.018247
gnus-point-at-eol 9568 0.0170039999 1.777...e-06
gnus-summary-setup-buffer 1 0.016208 0.016208
gnus-summary-mode 1 0.015669 0.015669
gnus-thread-sort-by-number 7148 0.0151860000 2.124...e-06
gnus-summary-initial-limit 1 0.014236 0.014236
gnus-xmas-menu-add-1 2 0.011324 0.005662
gnus-xmas-summary-menu-add 1 0.00966 0.00966
gnus-summary-limit-children 1191 0.0080060000 6.722...e-06
gnus-group-update-group 1 0.004549 0.004549
gnus-topic-update-topic-line 3 0.004531 0.0015103333
gnus-group-find-parameter 9 0.0034619999 0.0003846666
gnus-sort-gathered-threads 1 0.002755 0.002755
gnus-group-topic-parameters 9 0.002513 0.0002792222
gnus-topic-update-topics-containing-group 1 0.002433 0.002433
gnus-group-fast-parameter 7 0.002307 0.0003295714
gnus-correct-substring 17 0.002261 0.000133
gnus-compress-sequence 5 0.00214 0.000428
gnus-summary-highlight-line-0 1191 0.0020390000 1.712...e-06
gnus-point-at-bol 1214 0.0020160000 1.660...e-06
gnus-message 10 0.001997 0.0001997
gnus-agent-mode 1 0.001817 0.001817
gnus-xmas-agent-summary-menu-add 1 0.001682 0.001682
gnus-make-threads 1 0.001586 0.001586
gnus-articles-to-read 1 0.001552 0.001552
gnus-summary-auto-select-subject 1 0.001551 0.001551
gnus-summary-first-unread-subject 1 0.001539 0.001539
gnus-summary-first-subject 1 0.001486 0.001486
gnus-possibly-score-headers 1 0.001468 0.001468
gnus-topic-insert-topic-line 3 0.001403 0.0004676666
gnus-all-score-files 1 0.001387 0.001387
gnus-topic-hierarchical-parameters 9 0.001315 0.0001461111
gnus-update-summary-mark-positions 2 0.001297 0.0006485
gnus-configure-windows 1 0.001202 0.001202
gnus-group-insert-group-line-info 1 0.00112 0.00112
gnus-group-insert-group-line 1 0.001083 0.001083
gnus-summary-insert-line 2 0.001058 0.000529
gnus-summary-setup-default-charset 1 0.001049 0.001049
gnus-topic-parent-topic 100 0.0010250000 1.025...e-05
gnus-adjust-marked-articles 1 0.0009859999 0.0009859999
gnus-compute-unseen-list 1 0.000965 0.000965
gnus-inverse-list-range-intersection 1 0.000957 0.000957
gnus-list-range-difference 1 0.00095 0.00095
gnus-uncompress-range 3 0.000851 0.0002836666
gnus-killed-articles 1 0.000713 0.000713
gnus-current-topics 9 0.000701 7.788...e-05
gnus-parameter-charset 1 0.000648 0.000648
gnus-current-topic 9 0.0006109999 6.788...e-05
gnus-add-text-properties 7 0.000595 8.500...e-05
gnus-score-find-bnews 1 0.000583 0.000583
gnus-xmas-add-text-properties 7 0.000548 7.828...e-05
gnus-set-mode-line 1 0.000509 0.000509
gnus-sorted-difference 2 0.000507 0.0002535
gnus-update-format-specifications 2 0.000488 0.000244
gnus-group-auto-expirable-p 1 0.000456 0.000456
gnus-set-global-variables 3 0.000451 0.0001503333
gnus-topic-find-topology 60 0.0004170000 6.950...e-06
gnus-summary-position-point 3 0.000413 0.0001376666
gnus-topic-parameters 27 0.0004079999 1.511...e-05
gnus-goto-colon 3 0.000394 0.0001313333
gnus-group-set-mode-line 2 0.000379 0.0001895
gnus-parameter-ignored-charsets 1 0.000378 0.000378
gnus-summary-set-local-parameters 1 0.000353 0.000353
gnus-xmas-setup-summary-toolbar 1 0.000333 0.000333
gnus-sorted-union 1 0.00033 0.00033
gnus-group-goto-group 9 0.000316 3.511...e-05
gnus-continuum-version 4 0.000305 7.625e-05
gnus-find-method-for-group 17 0.0003 1.764...e-05
gnus-topic-goto-topic 4 0.000276 6.900...e-05
gnus-configure-frame 2 0.000262 0.000131
gnus-group-highlight-line 1 0.000259 0.000259
gnus-group-decoded-name 6 0.000258 4.299...e-05
gnus-apply-kill-file 1 0.000241 0.000241
gnus-dribble-enter 1 0.000233 0.000233
gnus-agent-load-alist 1 0.00022 0.00022
gnus-cache-articles-in-group 1 0.000215 0.000215
gnus-last-element 1 0.000198 0.000198
gnus-update-read-articles 1 0.000187 0.000187
gnus-group-name-charset 7 0.000179 2.557...e-05
gnus-agent-article-name 1 0.000178 0.000178
gnus-agent-group-pathname 1 0.000157 0.000157
gnus-news-group-p 1 0.000155 0.000155
gnus-cache-file-name 1 0.000153 0.000153
gnus-group-parameter-value 20 0.000148 7.400...e-06
gnus-group-topic-unread 8 0.000141 1.7625e-05
gnus-newsgroup-kill-file 2 0.000134 6.7e-05
gnus-group-get-parameter 15 0.000132 8.799...e-06
gnus-set-work-buffer 2 0.000121 6.05e-05
gnus-score-score-files 1 0.000119 0.000119
gnus-remassoc 12 0.000108 9e-06
gnus-newsgroup-directory-form 2 0.000102 5.1e-05
gnus-sort-score-files 1 0.000101 0.000101
gnus-summary-set-display-table 1 0.0001 0.0001
gnus-group-prefixed-name 2 9.8e-05 4.9e-05
gnus-summary-make-local-variables 2 9.499...e-05 4.75e-05
gnus-xmas-summary-set-display-table 1 9.399...e-05 9.399...e-05
gnus-check-server 1 9.3e-05 9.3e-05
gnus-set-difference 1 9.1e-05 9.1e-05
gnus-summary-buffer-name 2 9.1e-05 4.55e-05
gnus-short-group-name 1 8.6e-05 8.6e-05
gnus-parameters-get-parameter 2 8.500...e-05 4.25e-05
gnus-request-type 1 8.500...e-05 8.500...e-05
gnus-server-opened 1 8.4e-05 8.4e-05
gnus-score-file-name 1 8.3e-05 8.3e-05
gnus-update-alist-soft 4 8.2e-05 2.05e-05
gnus-thread-loop-p 28 7.699...e-05 2.749...e-06
gnus-buffer-live-p 6 7.3e-05 1.216...e-05
gnus-score-headers 1 6.600...e-05 6.600...e-05
gnus-all-windows-visible-p 1 6.600...e-05 6.600...e-05
gnus-prin1-to-string 1 6.2e-05 6.2e-05
gnus-make-hashtable 2 6e-05 3e-05
gnus-agent-get-undownloaded-list 1 5.8e-05 5.8e-05
gnus-xmas-switch-horizontal-scrollbar-off 1 5.8e-05 5.8e-05
gnus-score-load-files 1 5.6e-05 5.6e-05
gnus-get-buffer-create 3 5.6e-05 1.866...e-05
gnus-group-topic-p 1 5.3e-05 5.3e-05
gnus-group-topic-level 3 5.100...e-05 1.7e-05
gnus-member-of-valid 2 5e-05 2.5e-05
gnus-mode-line-buffer-identification 3 5e-05 1.666...e-05
gnus-group-group-name 2 4.9e-05 2.45e-05
gnus-score-load-file 1 4.8e-05 4.8e-05
gnus-ephemeral-group-p 2 4.8e-05 2.4e-05
gnus-get-function 2 4.6e-05 2.3e-05
gnus-topic-find-groups 3 4.599...e-05 1.533...e-05
gnus-group-topic-name 1 4.4e-05 4.4e-05
gnus-newsgroup-savable-name 2 4.2e-05 2.1e-05
gnus-group-set-parameter 1 4.2e-05 4.2e-05
gnus-remove-from-range 3 4e-05 1.333...e-05
gnus-group-group-indentation 2 3.9e-05 1.95e-05
gnus-summary-make-menu-bar 1 3.8e-05 3.8e-05
gnus-topic-visible-p 3 3.8e-05 1.266...e-05
gnus-get-buffer-window 1 3.7e-05 3.7e-05
gnus-agent-get-function 4 3.5e-05 8.750...e-06
gnus-xmas-mode-line-buffer-identification 3 3.1e-05 1.033...e-05
gnus-turn-off-edit-menu 1 3e-05 3e-05
gnus-methods-using 2 3e-05 1.5e-05
gnus-group-timestamp-delta 1 2.9e-05 2.9e-05
gnus-cache-file-contents 1 2.7e-05 2.7e-05
gnus-range-length 4 2.6e-05 6.5e-06
gnus-copy-sequence 5 2.4e-05 4.8e-06
gnus-group-quit-config 1 2.3e-05 2.3e-05
gnus-extent-start-open 1 2.2e-05 2.2e-05
gnus-virtual-group-p 1 2.2e-05 2.2e-05
gnus-group-set-info 1 2.1e-05 2.1e-05
gnus-visual-p 7 2.1e-05 3e-06
gnus-online 5 1.6e-05 3.200...e-06
gnus-cut-threads 1 1.6e-05 1.6e-05
gnus-xmas-extent-start-open 1 1.4e-05 1.4e-05
gnus-group-name-decode 8 1.4e-05 1.75e-06
gnus-list-of-unread-articles 2 1.3e-05 6.5e-06
gnus-undo-register 1 1.2e-05 1.2e-05
gnus-simplify-mode-line 1 1.1e-05 1.1e-05
gnus-create-hash-size 2 1e-05 5e-06
gnus-topic-update-unreads 3 9.999...e-06 3.333...e-06
gnus-info-set-entry 4 9.999...e-06 2.5e-06
gnus-undo-boundary 2 9e-06 4.5e-06
gnus-get-unread-articles-in-group 1 9e-06 9e-06
gnus-server-equal 2 9e-06 4.5e-06
gnus-server-to-method 3 9e-06 3e-06
gnus-server-add-address 1 8e-06 8e-06
gnus-frames-on-display-list 1 8e-06 8e-06
gnus-score-file-regexp 1 7e-06 7e-06
gnus-make-local-hook 1 7e-06 7e-06
gnus-use-long-file-name 4 6.999...e-06 1.75e-06
gnus-article-mark-to-type 3 6.999...e-06 2.333...e-06
gnus-home-score-file 2 6e-06 3e-06
gnus-expand-group-parameters 2 6e-06 3e-06
gnus-group-remove-parameter 1 5e-06 5e-06
gnus-undo-register-1 1 5e-06 5e-06
gnus-agent-method-p 2 5e-06 2.5e-06
gnus-window-to-buffer-helper 2 5e-06 2.5e-06
gnus-windows-old-to-new 1 4e-06 4e-06
gnus-make-sort-function 1 4e-06 4e-06
gnus-sorted-nintersection 1 4e-06 4e-06
gnus-sorted-ndifference 2 4e-06 2e-06
gnus-set-default-directory 1 3e-06 3e-06
gnus-make-thread-indent-array 1 3e-06 3e-06
gnus-remove-if 1 3e-06 3e-06
gnus-server-status 1 3e-06 3e-06
gnus-score-find-alist 1 3e-06 3e-06
gnus-update-missing-marks 1 2e-06 2e-06
gnus-agent-summary-make-menu-bar 1 2e-06 2e-06
gnus-summary-maybe-hide-threads 1 2e-06 2e-06
gnus-sorted-nunion 1 2e-06 2e-06
gnus-summary-make-tool-bar 1 2e-06 2e-06
gnus-group-remove-excess-properties 1 2e-06 2e-06
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-09 0:14 Entering nnimap group got much slower with 5.10 Gleb Arshinov
@ 2003-05-09 9:53 ` Simon Josefsson
2003-05-09 19:58 ` Gleb Arshinov
0 siblings, 1 reply; 19+ messages in thread
From: Simon Josefsson @ 2003-05-09 9:53 UTC (permalink / raw)
Cc: ding
Gleb Arshinov <gleb-usenet-g.ding-2003.05.08@usenet.barsook.com> writes:
> Just upgraded to 5.10.2 from Oort 0.08. I erased .newsrc.eld and ~/News
> to do a clean upgrade.
>
> Entering a large (~1200 messages, most with ! mark) IMAP newsgroup
> now takes a very long time (elp results included below). Most of this
> time modleline indicates "Fetching headers", which is unexpected (they
> should be all cached). If I (setq gnus-agent-mode nil), I get good
> performance (~1s to enter), but then I trigger old "nnimap eats all
> email" bug.
Try removing the setq, and agentize your nnimap server (`J a' in
server buffer). The header cache is now provided via the agent.
Unfortunately, this means that if you for some reason don't agentize
your nnimap server, you must re-enable nnimap-nov-is-evil to get the
old header cache code back.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-09 9:53 ` Simon Josefsson
@ 2003-05-09 19:58 ` Gleb Arshinov
2003-05-09 20:51 ` Simon Josefsson
2003-05-10 2:26 ` Lloyd Zusman
0 siblings, 2 replies; 19+ messages in thread
From: Gleb Arshinov @ 2003-05-09 19:58 UTC (permalink / raw)
>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>> Entering a large (~1200 messages, most with ! mark) IMAP
>> newsgroup now takes a very long time (elp results included
>> below). Most of this time modleline indicates "Fetching
>> headers", which is unexpected (they should be all cached). If
>> I (setq gnus-agent-mode nil), I get good performance (~1s to
>> enter), but then I trigger old "nnimap eats all email" bug.
Simon> Try removing the setq, and agentize your nnimap server (`J
Simon> a' in server buffer). The header cache is now provided via
Simon> the agent. Unfortunately, this means that if you for some
Simon> reason don't agentize your nnimap server, you must
Simon> re-enable nnimap-nov-is-evil to get the old header cache
Simon> code back.
Thanks Simon, it worked just as you described. Any reason why
agentizing all nnimap servers by default would be a bad thing?
Gleb
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Entering nnimap group got much slower with 5.10
2003-05-09 19:58 ` Gleb Arshinov
@ 2003-05-09 20:51 ` Simon Josefsson
2003-05-09 21:10 ` Gleb Arshinov
2003-05-10 2:26 ` Lloyd Zusman
1 sibling, 1 reply; 19+ messages in thread
From: Simon Josefsson @ 2003-05-09 20:51 UTC (permalink / raw)
Cc: ding
Gleb Arshinov <gleb-usenet-g.ding-2003.05.09@usenet.barsook.com> writes:
>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
> >> Entering a large (~1200 messages, most with ! mark) IMAP
> >> newsgroup now takes a very long time (elp results included
> >> below). Most of this time modleline indicates "Fetching
> >> headers", which is unexpected (they should be all cached). If
> >> I (setq gnus-agent-mode nil), I get good performance (~1s to
> >> enter), but then I trigger old "nnimap eats all email" bug.
>
> Simon> Try removing the setq, and agentize your nnimap server (`J
> Simon> a' in server buffer). The header cache is now provided via
> Simon> the agent. Unfortunately, this means that if you for some
> Simon> reason don't agentize your nnimap server, you must
> Simon> re-enable nnimap-nov-is-evil to get the old header cache
> Simon> code back.
>
> Thanks Simon, it worked just as you described. Any reason why
> agentizing all nnimap servers by default would be a bad thing?
New nnimap servers are agentized by default, I think, but perhaps old
servers aren't. If so, I wonder why more people haven't reported
this.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-09 20:51 ` Simon Josefsson
@ 2003-05-09 21:10 ` Gleb Arshinov
2003-05-10 13:21 ` Kai Großjohann
0 siblings, 1 reply; 19+ messages in thread
From: Gleb Arshinov @ 2003-05-09 21:10 UTC (permalink / raw)
>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
Simon> New nnimap servers are agentized by default, I think, but
Simon> perhaps old servers aren't. If so, I wonder why more
Simon> people haven't reported this.
I did a totally blank install for the upgrade (I wiped out .newsrc
.newsrc.eld and ~/News). Perhaps it is because my nnimap server is
defined in my .emacs?
(setq gnus-secondary-select-methods
'((nnimap "pivia.com"
(nnimap-address "mercury.pivia.com")
(nnimap-expunge-on-close 'never))))
Gleb
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-09 19:58 ` Gleb Arshinov
2003-05-09 20:51 ` Simon Josefsson
@ 2003-05-10 2:26 ` Lloyd Zusman
2003-05-10 14:06 ` Kai Großjohann
1 sibling, 1 reply; 19+ messages in thread
From: Lloyd Zusman @ 2003-05-10 2:26 UTC (permalink / raw)
Gleb Arshinov <gleb-usenet-g.ding-2003.05.09@usenet.barsook.com> writes:
>
> [ ... ]
>
> Thanks Simon, it worked just as you described. Any reason why
> agentizing all nnimap servers by default would be a bad thing?
>
> Gleb
I've never agentized anything in my life, nor have I wanted to.
Therefore, I don't have a clue as to what the ramifications of
agentizing my nnimap servers would be.
Could someone explain to me what would be different about my day-to-day
Gnus experience if I start to agentize nnimap? Will I have to start
using different commands and key sequences? Will I have to remember to
manually perform new functions that I never had to think about before in
order to read the messages my nnimap groups? Or (I hope!) could all
this agentizing-related stuff be accomplished via configuration, so that
all my commands for accessing the messages in these groups would still
be the same as always, with no exceptions?
These are not rhetorical questions. I understand what agentizing is,
but I truly don't know anything about the user experience of dealing
with agentized groups.
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-10 2:26 ` Lloyd Zusman
@ 2003-05-10 14:06 ` Kai Großjohann
2003-05-10 21:43 ` Lloyd Zusman
0 siblings, 1 reply; 19+ messages in thread
From: Kai Großjohann @ 2003-05-10 14:06 UTC (permalink / raw)
Lloyd Zusman <ljz@asfast.com> writes:
> Could someone explain to me what would be different about my day-to-day
> Gnus experience if I start to agentize nnimap?
Well, agentizing means that you can use Agent commands. You don't
have to use them, but if you don't use any Agent commands, the
corresponding action will not happen.
But I think that the Agent will function as a header cache out of the
box, without having to execute any extra commands at all. This means
that Gnus will download the headers when you first enter a group and
cache them locally. Then, when you enter the group again, Gnus will
use the headers from the local cache and only download the headers
that are missing from the local cache.
You can also tell Gnus to download all articles that you read and
cache them locally. This means that looking at those articles a
second time will be faster. But this is not the default
configuration, you have to add a line to ~/.gnus.
Everything else requires that you press new keys.
But it's not that difficult. Here is how I normally use Gnus when I
commute:
(1) I start Emacs and Gnus (in plugged mode, ie, normally).
(2) I hit `J s' to tell Gnus to fetch all articles.
(3) I hit `J j' to go unplugged and then hibernate my laptop.
(4) In the train, I wake up the laptop and read the previously-
downloaded articles and respond to them and so on.
(5) At the end of the train ride, I hibernate the laptop again.
(6) In the office, I do `J j' to go plugged. Then I use `J S' to
send all mails and postings composed in the train.
So the only Agent-specific keys I hit during the whole session are
these: `J s' -- `J j' -- `J j' -- `J S'
I find that rather convenient, considering that it gives me offline
functionality.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Entering nnimap group got much slower with 5.10
2003-05-10 14:06 ` Kai Großjohann
@ 2003-05-10 21:43 ` Lloyd Zusman
2003-05-10 23:38 ` Simon Josefsson
2003-05-12 15:44 ` Kai Großjohann
0 siblings, 2 replies; 19+ messages in thread
From: Lloyd Zusman @ 2003-05-10 21:43 UTC (permalink / raw)
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Could someone explain to me what would be different about my day-to-day
>> Gnus experience if I start to agentize nnimap?
>
> [ ... complete and very useful explanation ... ]
Thank you very much.
I never use gnus in "offline" mode, and so this lets me know that I
would have to signficantly change my gnus habits if I were to agentize
my nnimap groups in order to take advantage of caching.
So is there no way that this caching behavior for nnimap groups could be
made available to us non-agentizing users, in a way that doesn't require
any issuance of any agentizing-related commands?
--
Lloyd Zusman
ljz@asfast.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-10 21:43 ` Lloyd Zusman
@ 2003-05-10 23:38 ` Simon Josefsson
2003-05-11 0:04 ` Lloyd Zusman
2003-05-12 8:47 ` Niklas Morberg
2003-05-12 15:44 ` Kai Großjohann
1 sibling, 2 replies; 19+ messages in thread
From: Simon Josefsson @ 2003-05-10 23:38 UTC (permalink / raw)
Cc: ding
Lloyd Zusman <ljz@asfast.com> writes:
> I never use gnus in "offline" mode, and so this lets me know that I
> would have to signficantly change my gnus habits if I were to agentize
> my nnimap groups in order to take advantage of caching.
Your habits must be different from mine then, because I couldn't
normally tell whether Gnus was agentized or not. (Well, it is slower
if I don't agentize it...)
> So is there no way that this caching behavior for nnimap groups could be
> made available to us non-agentizing users, in a way that doesn't require
> any issuance of any agentizing-related commands?
(setq nnimap-nov-is-evil nil)
Why exactly didn't you want to agentize the nnimap server? Except for
the summary buffer color issue, I don't see where it would behave any
different. Hm. Except that it soaks up disk space, but the NOV cache
does that too, of course.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-10 23:38 ` Simon Josefsson
@ 2003-05-11 0:04 ` Lloyd Zusman
2003-05-11 3:04 ` Mark A. Hershberger
2003-05-12 8:47 ` Niklas Morberg
1 sibling, 1 reply; 19+ messages in thread
From: Lloyd Zusman @ 2003-05-11 0:04 UTC (permalink / raw)
Simon Josefsson <jas@extundo.com> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> [ ... ]
>>
>> So is there no way that this caching behavior for nnimap groups could be
>> made available to us non-agentizing users, in a way that doesn't require
>> any issuance of any agentizing-related commands?
>
> (setq nnimap-nov-is-evil nil)
>
> Why exactly didn't you want to agentize the nnimap server? Except for
> the summary buffer color issue, I don't see where it would behave any
> different. Hm. Except that it soaks up disk space, but the NOV cache
> does that too, of course.
Well, unless I misunderstood Kai's post, it seems like if I agentize the
nnimap server, I then have to enter a number of commands that I normally
don't use, if I want to read and manage the nnimap groups. If at all
possible, I don't want to start using this extra set of commands,
especially because I never use gnus in offline mode.
Or is my understanding incomplete? Is there a way to use an agentized
nnimap server without having to make use of any of those extra
"agentize" commands when I read, post, and reply to nnimap messages?
--
Lloyd Zusman
ljz@asfast.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-11 0:04 ` Lloyd Zusman
@ 2003-05-11 3:04 ` Mark A. Hershberger
2003-05-11 3:33 ` Lloyd Zusman
0 siblings, 1 reply; 19+ messages in thread
From: Mark A. Hershberger @ 2003-05-11 3:04 UTC (permalink / raw)
Lloyd Zusman <ljz@asfast.com> writes:
> Or is my understanding incomplete? Is there a way to use an agentized
> nnimap server without having to make use of any of those extra
> "agentize" commands when I read, post, and reply to nnimap messages?
To me, it seems that those extra commands that Kai uses, he uses
because he wants to deal with mail on the train when he isn't
connected.
I'm in the process of rebuilding my IMAP folders under the new Gnus
and find that its default agentizing /is/ faster.
Mark.
--
As long as you have mystery you have health; when you destroy mystery
you create morbidity. -- G.K. Chesterson
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-11 3:04 ` Mark A. Hershberger
@ 2003-05-11 3:33 ` Lloyd Zusman
2003-05-11 4:22 ` Harry Putnam
2003-05-11 9:57 ` Simon Josefsson
0 siblings, 2 replies; 19+ messages in thread
From: Lloyd Zusman @ 2003-05-11 3:33 UTC (permalink / raw)
mah@everybody.org (Mark A. Hershberger) writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Or is my understanding incomplete? Is there a way to use an agentized
>> nnimap server without having to make use of any of those extra
>> "agentize" commands when I read, post, and reply to nnimap messages?
>
> To me, it seems that those extra commands that Kai uses, he uses
> because he wants to deal with mail on the train when he isn't
> connected.
>
> I'm in the process of rebuilding my IMAP folders under the new Gnus
> and find that its default agentizing /is/ faster.
>
> Mark.
OK. So now I understand that my day-to-day gnus experience won't be any
different when using an agentized nnimap server, at least with regard to
the commands I need to issue for reading, posting, replying, etc.
So in order to set this up, are these the only things I have to do?
- make sure that the gnus-agent variable is set to t when
starting gnus
- do a 'J s' in the server buffer for each nnimap group that I
wish to agentize
--
Lloyd Zusman
ljz@asfast.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-11 3:33 ` Lloyd Zusman
@ 2003-05-11 4:22 ` Harry Putnam
2003-05-11 9:57 ` Simon Josefsson
1 sibling, 0 replies; 19+ messages in thread
From: Harry Putnam @ 2003-05-11 4:22 UTC (permalink / raw)
Lloyd Zusman <ljz@asfast.com> writes:
> mah@everybody.org (Mark A. Hershberger) writes:
>
>> Lloyd Zusman <ljz@asfast.com> writes:
>>
>>> Or is my understanding incomplete? Is there a way to use an agentized
>>> nnimap server without having to make use of any of those extra
>>> "agentize" commands when I read, post, and reply to nnimap messages?
>>
>> To me, it seems that those extra commands that Kai uses, he uses
>> because he wants to deal with mail on the train when he isn't
>> connected.
>>
>> I'm in the process of rebuilding my IMAP folders under the new Gnus
>> and find that its default agentizing /is/ faster.
>>
>> Mark.
>
> OK. So now I understand that my day-to-day gnus experience won't be any
> different when using an agentized nnimap server, at least with regard to
> the commands I need to issue for reading, posting, replying, etc.
>
> So in order to set this up, are these the only things I have to do?
>
> - make sure that the gnus-agent variable is set to t when
> starting gnus
>
> - do a 'J s' in the server buffer for each nnimap group that I
^^^
Maybe a typo but it should be `J a'
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: Entering nnimap group got much slower with 5.10
2003-05-11 3:33 ` Lloyd Zusman
2003-05-11 4:22 ` Harry Putnam
@ 2003-05-11 9:57 ` Simon Josefsson
2003-05-11 14:10 ` Lloyd Zusman
1 sibling, 1 reply; 19+ messages in thread
From: Simon Josefsson @ 2003-05-11 9:57 UTC (permalink / raw)
Cc: ding
Lloyd Zusman <ljz@asfast.com> writes:
> OK. So now I understand that my day-to-day gnus experience won't be any
> different when using an agentized nnimap server, at least with regard to
> the commands I need to issue for reading, posting, replying, etc.
Yes. If you discover anything else, please mention it.
> So in order to set this up, are these the only things I have to do?
>
> - make sure that the gnus-agent variable is set to t when
> starting gnus
Yup. (It is the default.)
> - do a 'J s' in the server buffer for each nnimap group that I
> wish to agentize
`J a'.
If you have never used the Agent before (~/News/agent/lib/servers
doesn't exist) this should happen automatically. I guess you at some
point (before the agent revamp in Oort) tried the Agent, and it left a
.../servers file around that is now inhibiting the auto-adding of
nntp/nnimap groups. This is probably why not more people are seeing
the slowdown -- for them, the agent is enabled for nnimap groups out
of the box.
It might be easier to simply rm -r ~/News/agent and restart Gnus.
(This should be possible to do at any time, I believe Gnus regenerates
all agent files if they are missing.)
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-11 9:57 ` Simon Josefsson
@ 2003-05-11 14:10 ` Lloyd Zusman
0 siblings, 0 replies; 19+ messages in thread
From: Lloyd Zusman @ 2003-05-11 14:10 UTC (permalink / raw)
Simon Josefsson <jas@extundo.com> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> OK. So now I understand that my day-to-day gnus experience won't be any
>> different when using an agentized nnimap server, at least with regard to
>> the commands I need to issue for reading, posting, replying, etc.
>
> Yes. If you discover anything else, please mention it.
Will do.
>> So in order to set this up, are these the only things I have to do?
>>
>> - make sure that the gnus-agent variable is set to t when
>> starting gnus
>
> Yup. (It is the default.)
I had set that variable to nil ages ago because of some problems that
were occurring back then. I don't recall what those problems were, but
at the time (probably more than a year ago), they kept me from starting
gnus.
But it's fixed now ... setting gnus-agent to t works just fine.
>> - do a 'J s' in the server buffer for each nnimap group that I
>> wish to agentize
>
> `J a'.
>
> If you have never used the Agent before (~/News/agent/lib/servers
> doesn't exist) this should happen automatically. I guess you at some
> point (before the agent revamp in Oort) tried the Agent, and it left a
> .../servers file around that is now inhibiting the auto-adding of
> nntp/nnimap groups. This is probably why not more people are seeing
> the slowdown -- for them, the agent is enabled for nnimap groups out
> of the box.
Indeed. I had a slew of things under ~/News/agent before retrying this.
However, once I did the `J a' (when said `J s' it was a typo),
everything speeded up in my nnimap groups. Perhaps some of the ancient
stuff that had been created by the non-working agent code had inhibited
the proper working of the agent until I did the `J a' last night.
> It might be easier to simply rm -r ~/News/agent and restart Gnus.
> (This should be possible to do at any time, I believe Gnus regenerates
> all agent files if they are missing.)
I just did this. It worked fine. Thanks.
However, what got created was this:
~/News/agent/nnimap
Under it is a subdirectory for each of the nnimap servers that I'm
using, and in each of these subdirectories is a subdirectory for each of
the individual nnimap groups, plus one additional subdirectory called
`agent,lib'. That is ...
~/News/agent/nnimap
~/News/agent/nnimap/email ("email" is one of my nnimap server names)
~/News/agent/nnimap/email/INBOX.gnus
~/News/agent/nnimap/email/INBOX.ruby
~/News/agent/nnimap/email/INBOX.[whatever]
~/News/agent/nnimap/email/agent.lib
--
Lloyd Zusman
ljz@asfast.com
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-10 23:38 ` Simon Josefsson
2003-05-11 0:04 ` Lloyd Zusman
@ 2003-05-12 8:47 ` Niklas Morberg
2003-05-12 11:55 ` Simon Josefsson
1 sibling, 1 reply; 19+ messages in thread
From: Niklas Morberg @ 2003-05-12 8:47 UTC (permalink / raw)
Simon Josefsson <jas@extundo.com> writes:
> Why exactly didn't you want to agentize the nnimap server?
In my case, I used the agent for a couple of weeks, but it
forgot my marks which required me to remark a bunch of
emails. Since then I have stopped using the agent. See
<URL: http://article.gmane.org/gmane.emacs.gnus.general/51217>
Niklas
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-12 8:47 ` Niklas Morberg
@ 2003-05-12 11:55 ` Simon Josefsson
0 siblings, 0 replies; 19+ messages in thread
From: Simon Josefsson @ 2003-05-12 11:55 UTC (permalink / raw)
Niklas Morberg <niklas.morberg@axis.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Why exactly didn't you want to agentize the nnimap server?
>
> In my case, I used the agent for a couple of weeks, but it
> forgot my marks which required me to remark a bunch of
> emails. Since then I have stopped using the agent. See
> <URL: http://article.gmane.org/gmane.emacs.gnus.general/51217>
Ouch. I haven't experienced this, but I don't use expiring so perhaps
that triggers it. Anyone else using expire marks with the agent, in
nnimap?
As for the problem with deleted messages sticking around, I used to
see this too but it seems to have gone away now.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Entering nnimap group got much slower with 5.10
2003-05-10 21:43 ` Lloyd Zusman
2003-05-10 23:38 ` Simon Josefsson
@ 2003-05-12 15:44 ` Kai Großjohann
1 sibling, 0 replies; 19+ messages in thread
From: Kai Großjohann @ 2003-05-12 15:44 UTC (permalink / raw)
Lloyd Zusman <ljz@asfast.com> writes:
> I never use gnus in "offline" mode, and so this lets me know that I
> would have to signficantly change my gnus habits if I were to agentize
> my nnimap groups in order to take advantage of caching.
What do you want to cache?
Headers are cached automatically. To make it cache automatically
articles that you read, do (add-hook 'gnus-select-article-hook
'gnus-agent-fetch-selected-article).
To make it cache automatically articles that you DON'T read (or
haven't read yet), you need to do `J s'.
To make it cache dirty dishes, you'll have to write some Lisp.
Was my explanation definicient, or do you want to cache dirty dishes?
--
This line is not blank.
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2003-05-12 15:44 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-09 0:14 Entering nnimap group got much slower with 5.10 Gleb Arshinov
2003-05-09 9:53 ` Simon Josefsson
2003-05-09 19:58 ` Gleb Arshinov
2003-05-09 20:51 ` Simon Josefsson
2003-05-09 21:10 ` Gleb Arshinov
2003-05-10 13:21 ` Kai Großjohann
2003-05-10 2:26 ` Lloyd Zusman
2003-05-10 14:06 ` Kai Großjohann
2003-05-10 21:43 ` Lloyd Zusman
2003-05-10 23:38 ` Simon Josefsson
2003-05-11 0:04 ` Lloyd Zusman
2003-05-11 3:04 ` Mark A. Hershberger
2003-05-11 3:33 ` Lloyd Zusman
2003-05-11 4:22 ` Harry Putnam
2003-05-11 9:57 ` Simon Josefsson
2003-05-11 14:10 ` Lloyd Zusman
2003-05-12 8:47 ` Niklas Morberg
2003-05-12 11:55 ` Simon Josefsson
2003-05-12 15:44 ` Kai Großjohann
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).