{"push_id":2338594694,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"669fb1152506a57d8d65e9f441f0b483cf37932f","before":"0be4d3711f65af9aea69fc8e3937bdaf36a4a73a","commits":[{"sha":"669fb1152506a57d8d65e9f441f0b483cf37932f","author":{"name":"Nickolai Zeldovich","email":"6f5dc8a016c54142941c91c12788c9d3785189b5@csail.mit.edu"},"message":"cmd/vuvuzela-client: be more precise in adjusting lastOut on ack\n\nPreviously, the sending sequence would restart from the lowest message\nwhen anything got ACKed.  In steady-state when there's no message\nloss, this resulted in stuttering: each message would get sent twice.\nWhen message 1 got acked, message 2 was already in-flight (and would have\nbeen acked soon), but resetting lastOut caused message 2 to be sent again.\n\nThe new behavior is to continue in the looping order of outstanding\nmessages.  In steady-state with no message loss, this should result in\n2x higher throughput by avoiding stuttering.","distinct":true,"url":"https://api.github.com/repos/vuvuzela/vuvuzela/commits/669fb1152506a57d8d65e9f441f0b483cf37932f"}]}
{"actor":{"display_login":"zeldovich"}}