| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Add latency profiling from 'important' marks |  Craig Tiller | 2016-07-19 |
| | | | | | | | | Allows seeing directly how long was spent: - running up to putting bytes on the wire - between sending and receiving - between receiving and finishing | ||
| * | slightly fancier output |  David Garcia Quintas | 2016-06-21 |
| | | |||
| * | use qps_json_driver for latency profiling | David Garcia Quintas | 2016-06-20 |
| | | |||
| * | Update copyrights | Craig Tiller | 2015-12-22 |
| | | |||
| * | Tweak run_latency_profile.sh to run better on Jenkins |  Craig Tiller | 2015-12-15 |
| | | | | | | | - More robustly run processes in the background - Detect and use pypy if available - Add a --latency_profile flag to control whether to run the latency profiling stuff | ||
| * | Lower latency profiling | Craig Tiller | 2015-11-03 |
| | | | | | | | | | Current latency profiles have their tails dominated by writing latency logs, which is hugely undesirable. Now when a thread log fills up, push it to a background thread to write to disk. At shutdown, wait for all latency traces to be flushed. | ||
| * | Remove extra line | Craig Tiller | 2015-10-12 |
| | | |||
| * | Simplify adding annotations, annotate more things | Craig Tiller | 2015-10-09 |
| | | |||
| * | Script to generate latency reports | Craig Tiller | 2015-10-08 |
 |
index : grpc | |
| RPC system from Google |
| aboutsummaryrefslogtreecommitdiffhomepage |