This is a heads up about the current situation with s4 (commons) and labsdb.
There's been more activity lately on s4, and that had made labsdb1011 (analytics role) start lagging behind.
I have tried to ease its weight a couple of days ago, to help it recovering:
The last change has (as sort of expected) made labsdb1010 lag:
I am going to decrease the pt-kill query time from 3600 to 1800 to see if that helps labsdb1010 to guard the fort a bit.
There's not much else we can do at the moment, but just keep all these issues in mind if people complain about lag on s4 (commons) on the analytics role.
The web role is doing fine (labsdb1009 isn't lagging).