/astat

[Skywing]

That limit isn't calculated per-user?

Uhm.. huh?  I just said that the "Too many server requests" was per-connection.

Anyways, my point is that there's far too much else going on for you to be able to accurately measure any possible differences in priority between /stat and/astat.

[Arta]

My point was that if the limit is calculated per-connection, irrespective of the actions of other users over other connections, then I don't see why that should be the case

In fact, it seems likely to me that the actions of other users are the most important. Perhaps /astat only affects priority when load on the servers reaches a certain point, or something?

Anyway, I suppose it's moot really, since we have no way to find out.

[Skywing]

My point was that if the limit is calculated per-connection, irrespective of the actions of other users over other connections, then I don't see why that should be the case

In fact, it seems likely to me that the actions of other users are the most important. Perhaps /astat only affects priority when load on the servers reaches a certain point, or something?

Anyway, I suppose it's moot really, since we have no way to find out.

The "Too many server requests" is unrelated

I was theorizing that /astat requests would be marked as "low priority", and that requests issued otherwise would be moved in front of them in the database server's queue.  This has nothing to do with the per-user restriction on number of queries per timeframe.