)]}'
{
  "commit": "99d46c5d2d9449e5ee7feaf73228ba989a9cd649",
  "tree": "5317341e57ed78a873989b4b2b9aafcb33fc8506",
  "parents": [
    "df1d3ca07d2d07bba352d5b73c4313b4e2a6203e"
  ],
  "author": {
    "name": "notcarl",
    "email": "notcarl@google.com",
    "time": "Mon Oct 03 23:47:50 2016 +0000"
  },
  "committer": {
    "name": "Joe Tsai",
    "email": "joetsai@digital-static.net",
    "time": "Wed Oct 12 12:43:44 2016 -0700"
  },
  "message": "Add protobuf benchmarks for varint encoding.\n\nWe add two sets of benchmarks:\n1. This benchmark uses increasingly large Any messages, which are common for storage systems.\nFor database like services, which are agnostic to the type being stored, Proto2 extensions could be used.\nHowever, Proto3 drops unknown fields and most of extensions, so Any must be used.\nAny types are also used as the arbitrary payload mechanism for RPC metadata.\n2. Another benchmark uses the barest possible proto, meant to show the overhead of the encoding system.\nThis is the default cost of encoding a proto with absolutely no fields.\n\nPiperOrigin-RevId: 135044506\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "78e40ddcef0ebb33d0b54a61d4502a759439362b",
      "new_mode": 33188,
      "new_path": "proto/encode_test.go"
    }
  ]
}