"Updating marks" spam -- how do I kill it?

"Updating marks" spam -- how do I kill it?

[Jack Twilley]

Every time I hit 'g', I get a line of "Updating marks" for each nnml
group I have.  This is remarkably annoying and inefficient.  Annoying
because it takes time and wastes bandwidth.  Inefficient because it
traverses every single group instead of only the ones that were
modified by the 'g'.

The marks changes aren't making many points with me.  I really hope
they're making *someone* happy.

Jack.
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash

Re: "Updating marks" spam -- how do I kill it?

[Kai Großjohann]

Jack Twilley <jmt+usenet@twilley.org> writes:

> Every time I hit 'g', I get a line of "Updating marks" for each nnml
> group I have.  This is remarkably annoying and inefficient.  Annoying
> because it takes time and wastes bandwidth.  Inefficient because it
> traverses every single group instead of only the ones that were
> modified by the 'g'.

IIUC, Simon wants to find bottlenecks and hence included the
messages.  I guess the messages will go away after Simon has found the
bottlenecks.

Maybe it doesn't actually do anything for each group, but just looks
at each group to see if something needs to be done?  Hm.  Simon?

kai
-- 
Symbol's function definition is void: signature

Re: "Updating marks" spam -- how do I kill it?

[Simon Josefsson]

Jack Twilley <jmt+usenet@twilley.org> writes:

> Every time I hit 'g', I get a line of "Updating marks" for each nnml
> group I have.  This is remarkably annoying and inefficient.  Annoying
> because it takes time and wastes bandwidth.

I changed the verbosity level to 8.

> Inefficient because it traverses every single group instead of only
> the ones that were modified by the 'g'.

The updating of marks isn't in the Gnus -> nnml direction, but rather
the other way around.  So all groups that are checked for new mail
have their marks updated (if necessary) as well.

Re: "Updating marks" spam -- how do I kill it?

[Jack Twilley]

>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:

Jack> Every time I hit 'g', I get a line of "Updating marks" for each
Jack> nnml group I have.  This is remarkably annoying and inefficient.
Jack> Annoying because it takes time and wastes bandwidth.

Simon> I changed the verbosity level to 8.

Tell me how to make it go away?

Jack> Inefficient because it traverses every single group instead of
Jack> only the ones that were modified by the 'g'.

Simon> The updating of marks isn't in the Gnus -> nnml direction, but
Simon> rather the other way around.  So all groups that are checked
Simon> for new mail have their marks updated (if necessary) as well.

There has *got* to be a better way.

Jack.
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash

Re: "Updating marks" spam -- how do I kill it?

[Paul Jarc]

Jack Twilley <jmt@twilley.org> wrote:
>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>Simon> The updating of marks isn't in the Gnus -> nnml direction, but
>Simon> rather the other way around.  So all groups that are checked
>Simon> for new mail have their marks updated (if necessary) as well.
> 
> There has *got* to be a better way.

When nnmaildir looks at the stored marks, it also grabs the modtime
and keeps that in memory.  Next time around, if the modtime hasn't
changed, the marks are assumed to be unchanged.


paul

Re: "Updating marks" spam -- how do I kill it?

[Simon Josefsson]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Jack Twilley <jmt+usenet@twilley.org> writes:
>
>> Every time I hit 'g', I get a line of "Updating marks" for each nnml
>> group I have.  This is remarkably annoying and inefficient.  Annoying
>> because it takes time and wastes bandwidth.  Inefficient because it
>> traverses every single group instead of only the ones that were
>> modified by the 'g'.
>
> IIUC, Simon wants to find bottlenecks and hence included the
> messages.  I guess the messages will go away after Simon has found the
> bottlenecks.
>
> Maybe it doesn't actually do anything for each group, but just looks
> at each group to see if something needs to be done?  Hm.  Simon?

The messages were added because some seem to wanted more information
on what was going on.  Right now it does actually do something for
each group (reads the .marks file for each group and copy the
information into Group Info) but this will change once I get a little
profiling info.

Re: "Updating marks" spam -- how do I kill it?

[Henrik Enberg]

Jack Twilley <jmt@twilley.org> writes:

>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
> Jack> Every time I hit 'g', I get a line of "Updating marks" for each
> Jack> nnml group I have.  This is remarkably annoying and inefficient.
> Jack> Annoying because it takes time and wastes bandwidth.
>
> Simon> I changed the verbosity level to 8.
>
> Tell me how to make it go away?

(setq gnus-verbose 7)

> Jack> Inefficient because it traverses every single group instead of
> Jack> only the ones that were modified by the 'g'.
>
> Simon> The updating of marks isn't in the Gnus -> nnml direction, but
> Simon> rather the other way around.  So all groups that are checked
> Simon> for new mail have their marks updated (if necessary) as well.
>
> There has *got* to be a better way.

Is there a way to se if a specific group has new messages?
`gnus-group-get-new-news' doesn't seem to differentiate between groups.

Henrik
-- 
Could I have a drug overdose?

Re: "Updating marks" spam -- how do I kill it?

[Simon Josefsson]

Jack Twilley <jmt@twilley.org> writes:

>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
> Jack> Every time I hit 'g', I get a line of "Updating marks" for each
> Jack> nnml group I have.  This is remarkably annoying and inefficient.
> Jack> Annoying because it takes time and wastes bandwidth.
>
> Simon> I changed the verbosity level to 8.
>
> Tell me how to make it go away?

It should be gone now, in CVS.

If you want to make the marks stuff go away completely, you can use
the `nnml-marks-is-evil' or `nnfolder-marks-is-evil' server variables.

> Jack> Inefficient because it traverses every single group instead of
> Jack> only the ones that were modified by the 'g'.
>
> Simon> The updating of marks isn't in the Gnus -> nnml direction, but
> Simon> rather the other way around.  So all groups that are checked
> Simon> for new mail have their marks updated (if necessary) as well.
>
> There has *got* to be a better way.

Yes: Only updating the marks if the file was modified since it checked
last time.  Making it so is in the pipe.  Is the current way causing
any problems other than inefficiency?  Soon all the extra work the
marks stuff require is an extra stat() to see if the marks file
changed or not, that shouldn't be too heavy compared to other things,
I hope.

Re: "Updating marks" spam -- how do I kill it?

[Kai Großjohann]

Jack Twilley <jmt@twilley.org> writes:

>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
> Jack> Every time I hit 'g', I get a line of "Updating marks" for each
> Jack> nnml group I have.  This is remarkably annoying and inefficient.
> Jack> Annoying because it takes time and wastes bandwidth.
>
> Simon> I changed the verbosity level to 8.
>
> Tell me how to make it go away?

Set gnus-verbose to something less than 8.

kai
-- 
Symbol's function definition is void: signature

Re: "Updating marks" spam -- how do I kill it?

[Henrik Enberg]

Henrik Enberg <henrik@enberg.org> writes:

>>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:

>> Simon> I changed the verbosity level to 8.
>>
>> Tell me how to make it go away?
>
> (setq gnus-verbose 7)

Hmm, looking at the code, I see that it should be
`gnus-verbose-backends', not `gnus-verbose'.

Henrik
-- 
Could I have a drug overdose?