{"push_id":1297267671,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d5ce2225173ec41804750d3de0211408ba096bb9","before":"6e1d81f60e79e915b674b84c821ec774b6f58286","commits":[{"sha":"d5ce2225173ec41804750d3de0211408ba096bb9","author":{"name":"sergeyu","email":"c87bced964a1a67135ef24f8859407c75a0e2aba@chromium.org"},"message":"Measure bandwidth utilization in the ScrollPerformance test\n\nNow ScrollPerformance also reports network bandwidth utilization.\n\nAlso removed two outdated tests: StreamFrameRate and IntermittentChanges.\nThese tests were intended mainly to evaluate performance of the PseudoTCP\nlayer and they were using verbatim video codec. They are not applicable\nfor WebRTC-based protocol. Also the protocol perf tests have been updated\nto use SoftwareVideoRenderer which allows to get FrameStats when using\nICE protocol and this approach is not compatible with the old tests.\n\nBandwidth utilization numbers I get currently with 8Mbps bandwidth:\nICE: 93%\nWebRTC: varies from 21 to 25%\n\nThe second number also goes to 32 when I change test length and warm-up\ntime to 5 seconds. This suggests that the problem is partly that the\nbandwidth estimate in WebRTC is below the actual bandwidth in the test and\nit takes a lot of time to ramp up.\n\nBUG=645656\n\nReview-Url: https://codereview.chromium.org/2338693002\nCr-Commit-Position: refs/heads/master@{#418444}","distinct":true,"url":"https://api.github.com/repos/dstockwell/chromium/commits/d5ce2225173ec41804750d3de0211408ba096bb9"}]}
{"actor":{"display_login":"dstockwell"}}