Change Details

With weights for api/recentchanges/vslow/etc groups being in terms of 0..1, it's impossible to do slow warmups of traffic to those groups. Configurations should be edited to change all `1` weights into `100` weights (scaling the few non-`1` weights as necessary). If done for all instances at once, this shouldn't have any impact. If it would be helpful I think I could come up with some shell scripting to automate this transformation. [] s1 [] s2 [] s3 [] s4 [] s5 [] s6 [] s7 [] s8

With weights for api/recentchanges/vslow/etc groups being in terms of 0..1, it's impossible to do slow warmups of traffic to those groups. Configurations should be edited to change all `1` weights into `100` weights (scaling the few non-`1` weights as necessary). If done for all instances at once, this shouldn't have any impact. If it would be helpful I think I could come up with some shell scripting to automate this transformation. [] s1 [] s2 [x] s3 [] s4 [] s5 [] s6 [] s7 [] s8

With weights for api/recentchanges/vslow/etc groups being in terms of 0..1, it's impossible to do slow warmups of traffic to those groups. Configurations should be edited to change all `1` weights into `100` weights (scaling the few non-`1` weights as necessary). If done for all instances at once, this shouldn't have any impact. If it would be helpful I think I could come up with some shell scripting to automate this transformation. [] s1 [] s2 [x] s3 [] s4 [] s5 [] s6 [] s7 [] s8