[mb-devel] requests limit

[Brian Schweitzer]

On Wed, Apr 2, 2008 at 5:06 PM, Aaron Cooper <cooperaa at gmail.com> wrote:
> On 2-Apr-08, at 12:08 PM, Bogdan Butnaru wrote:
>  > Hello!
>  >
>  > I have just received the following error message on the site while
>  > doing some voting:
>  >
>  >> Your requests are exceeding the allowable rate limit (13.0, limit
>  >> is 13.0 per 10 seconds)
>  >> Please slow down then try again.
>  >
>  > I'm using the "enhanced voting" GM script, which I'm sure was the
>  > cause. The script allows the user to vote/approve/comment on a single
>  > page of edits, without opening new pages. This can cause a burst of
>  > accesses when pressing "apply", which must have triggered some
>  > protection. However, the burst is very short—at most ten edits can
>  > receive notes/approves at one time, and then you'll stop for a while
>  > to vote on the next page—so it shouldn't be a problem for the site.
>  > Also, I think the script actually reduces bandwidth usage, because it
>  > no longer needs to display the intermediate pages (eg, for approving),
>  > it can send directly the input.
>  >
>  > So, would it be possible to raise a bit the limits that trigger the
>  > error? I think it can't send more than 21 (at most 10 (approvals or
>  > cancels), at most 10 edit notes, and one request for the next page of
>  > edits) at one time. So bursts of less then 30 or so edits (at any
>  > speed) should be ignored, provided that there's a pause of at least a
>  > few seconds between them. What do you think?
>
>  I've never seen this while voting with the Enhanced Voting GM script
>  but I have run into it often while opening up several artist pages
>  from my subscription mails.  Maybe your Firefox runs faster than mine :)

It tends to happen when you're leaving notes and/or approving - ie,
doing the things that trigger additional page loads.  It causes the
script to toss a bunch of 503 errors and/or the page to stop
responding (requiring a reload).

Brian