[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-30 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554


Tim Starling tstarl...@wikimedia.org changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||WONTFIX




--- Comment #11 from Tim Starling tstarl...@wikimedia.org  2009-12-01 
01:55:15 UTC ---
Reverted.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554


Tim Starling tstarl...@wikimedia.org changed:

   What|Removed |Added

 CC||tstarl...@wikimedia.org
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |




--- Comment #5 from Tim Starling tstarl...@wikimedia.org  2009-11-17 22:46:06 
UTC ---
I'm not keen on this. The idea of maxlag is to perform writes as fast as the
slowest slave will allow. If you keep doing writes until half the slaves are
overloaded, the slowest slaves will be past 30s lag and completely depooled.
That doesn't seem like an appropriate place to stop writing.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554


Andrew Garrett agarr...@wikimedia.org changed:

   What|Removed |Added

 CC||agarr...@wikimedia.org




--- Comment #6 from Andrew Garrett agarr...@wikimedia.org  2009-11-17 
22:50:59 UTC ---
(In reply to comment #0)
 Background:
 AWB has been (or is still, nearing finishing) reimplemented to use the api for
 editing. We've decided its wise to follow maxlag, more so for bot editing.
 
 So we are using the recommended value of 5ms for bot editing, but this became 
 a
 pain for users doing semi-automated editing, as they would quite often fall
 prey to maxlag restrictions preventing editing. We therefore changed this to
 20ms for users. Although, this solves some problems for users, it doesn't 
 solve
 them completely.. And in some cases, editing can be done (and following
 guidelines) using a multi tabbed browser and some fast clicking..

Do you mean 5 s? 5 ms is probably more than the latency between the master and
some slaves on a bad day.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554





--- Comment #7 from Reedy s...@reedyboy.net  2009-11-17 22:52:58 UTC ---
Yeah, i do. 5ms wouldn't be worth bothering about ;)


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554





--- Comment #8 from Roan Kattouw roan.katt...@gmail.com  2009-11-17 22:53:30 
UTC ---
I guess it kinda depends on how this is used, and the nature of the client.
Bots performing maintenance tasks can afford to wait for maxlag to drop, but
tools like AWB that aim to provide relatively fast user interaction don't want
to wait all day. In a scenario where one slave is badly lagged but the rest is
not, avglag could help for these slightly higher priority edits. Of course it
would need to be set to a low value like 2.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554





--- Comment #9 from Andrew Garrett agarr...@wikimedia.org  2009-11-17 
22:55:15 UTC ---
(In reply to comment #8)
 I guess it kinda depends on how this is used, and the nature of the client.
 Bots performing maintenance tasks can afford to wait for maxlag to drop, but
 tools like AWB that aim to provide relatively fast user interaction don't want
 to wait all day. In a scenario where one slave is badly lagged but the rest is
 not, avglag could help for these slightly higher priority edits. Of course it
 would need to be set to a low value like 2.

Well, if your approach is keep writing regardless of whether you lag a slave
out until it's depooled, then you might as well not bother checking for slave
lag at all.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-11-17 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554





--- Comment #10 from Tim Starling tstarl...@wikimedia.org  2009-11-17 
22:58:27 UTC ---
(In reply to comment #8)
 I guess it kinda depends on how this is used, and the nature of the client.
 Bots performing maintenance tasks can afford to wait for maxlag to drop, but
 tools like AWB that aim to provide relatively fast user interaction don't want
 to wait all day. In a scenario where one slave is badly lagged but the rest is
 not, avglag could help for these slightly higher priority edits. Of course it
 would need to be set to a low value like 2.

If they can't afford to wait, they should not specify a maxlag value. Then
they'll get the same lag policy as ordinary editors.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-09-15 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554





--- Comment #1 from Reedy s...@reedyboy.net  2009-09-15 20:04:40 UTC ---
Created an attachment (id=6554)
 -- (https://bugzilla.wikimedia.org/attachment.cgi?id=6554)
Attempt at implementing avglag

Patch attached as per IRC ;)


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-09-15 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554


Reedy s...@reedyboy.net changed:

   What|Removed |Added

Attachment #6554 is|0   |1
   obsolete||




--- Comment #2 from Reedy s...@reedyboy.net  2009-09-15 20:37:04 UTC ---
Created an attachment (id=6555)
 -- (https://bugzilla.wikimedia.org/attachment.cgi?id=6555)
Improvement on last patch, as per roans comments on irc, and other minor tweaks
noticed

A side point; i haven't added it to the maintenance patches where maxlag is
used..

IMHO it shouldn't be needed there?


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l


[Bug 20554] Expose average lag (avglag) a well as maxlag

2009-09-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=20554


Brion Vibber br...@wikimedia.org changed:

   What|Removed |Added

Summary|Implement avglag  |Expose average lag
   ||(avglag) a well as maxlag




-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.

___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l