)]}'
{
  "log": [
    {
      "commit": "7ec2c8a9b6f9a050d2ac9e0c35f0a631573f3de6",
      "tree": "289ddc73370f240d2feabf59fa855d11e04df3ce",
      "parents": [
        "1701d887aca0374c000a018a974227064e77d769"
      ],
      "author": {
        "name": "Christopher Ferris",
        "email": "cferris@google.com",
        "time": "Fri Apr 05 12:47:39 2019 -0700"
      },
      "committer": {
        "name": "Christopher Ferris",
        "email": "cferris@google.com",
        "time": "Fri Apr 05 14:45:15 2019 -0700"
      },
      "message": "Add malloc benchmarks.\n\nAdding some benchmarks that keep a certain number of allocation\naround. This benchmark should not be used as an absolute for determining\nwhat is a good/bad native allocator. However, it should be used to make\nsure that numbers are not completely changed between allocator versions.\n\nAlso update the malloc sql benchmark to match the same style as these\nnew benchmarks.\n\nBug: 129743239\n\nTest: Ran these benchmarks.\nChange-Id: I1995d98fd269b61d9c96efed6eff3ed278e24c97\n"
    },
    {
      "commit": "0dc784431b3e0a5964b257753e2bf4dcc96a463d",
      "tree": "112d7833549c2064988a53b6ad633117567bb6f3",
      "parents": [
        "5285d5995b37df589907b8fb00993b4414e7fd81"
      ],
      "author": {
        "name": "Christopher Ferris",
        "email": "cferris@google.com",
        "time": "Thu Aug 09 15:19:57 2018 -0700"
      },
      "committer": {
        "name": "Christopher Ferris",
        "email": "cferris@google.com",
        "time": "Tue Aug 14 16:01:58 2018 -0700"
      },
      "message": "Add new malloc benchmarks.\n\nThis runs through the trace of the allocations in a sql benchmark app\nexecuted in the benchmark thread.\n\nAdd one benchmark with decay time set to 0 and another with decay time\nset to 1.\n\nInclude a script that can generate a header file that can be used to\nregenerate the data.\n\nBug: 112317428\n\nTest: Builds, ran unit tests, ran benchmarks.\nChange-Id: I62e287cc06b74b74bcc5a4bbee71b0fac0a196fd\n"
    }
  ]
}