{"push_id":831754864,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a0325023f157e7da1023421fe59221c6fbe7306c","before":"bfdc2009619ff1c5dd84ce017c8a73d472734e5b","commits":[{"sha":"a0325023f157e7da1023421fe59221c6fbe7306c","author":{"email":"e64525f0749d51060e37ecf30bb67d5ec20f5b99@cs.stanford.edu","name":"Jonathan Ellithorpe"},"message":"Updated MeasurementClient to be distributed.\n\nMeasurementClient is now able to execute distributed tests using the same\nmaster / slave style of communication and control found in the RAMCloud cluster\nperformance benchmarks. The client with clientIndex=0 is the master, while the\nrest are the slaves. The master issues commands to slaves and receives\nresponses back from them through a signaling table in RAMCloud containing\nvarious registers for storing the command, its arguments, slaves return status,\nand slaves return values.\n\nCurrently there seems to be an occasional issue with timeouts firing during\ntests inolving around 7 or more clients, but that may be an issue with some of\nthe hardcoded timeout constants being too tight.","distinct":true,"url":"https://api.github.com/repos/ellitron/ramcloud-gremlin/commits/a0325023f157e7da1023421fe59221c6fbe7306c"}]}