Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: spam-report.el pinging too fast?
Date: Tue, 25 May 2004 00:40:34 +0200	[thread overview]
Message-ID: <m3iselh2jh.fsf@quimbies.gnus.org> (raw)

I just saw the load on spam.gmane.org go to 120, so I grepped through
the access.log, and saw lots of stuff from spam-report.el there.  :-)

Now, the problem is that spam.php is slow, because it tries to give
sensible feedback on duplicate reports and stuff.  spam-report.el
doesn't wait for any response, though, which means that a user that
has a lot of spam to report will drive up the load.

So there's two solutions to this: Either spam-report.el could wait
for a response (and serialize the reports), or I could write a new
"programmatic" spam.php that queues the reports and does the real
handling of them later.

What do you think?
 
-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




             reply	other threads:[~2004-05-24 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 22:40 Lars Magne Ingebrigtsen [this message]
2004-05-24 22:55 ` Lars Magne Ingebrigtsen
2004-05-25 11:23   ` Reiner Steib
2004-05-25 18:50   ` Ted Zlatanov

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=m3iselh2jh.fsf@quimbies.gnus.org \
    --to=larsi@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).