)]}'
{
  "commit": "8a44216e8bdad1a13ce637b1395467600870849a",
  "tree": "e702cd7071b7585c842326ef0a394e519e55f74d",
  "parents": [
    "001d747419a87e1431e6aae3f1e815f843ee6e51"
  ],
  "author": {
    "name": "Matthias Sohn",
    "email": "matthias.sohn@sap.com",
    "time": "Fri Jun 05 13:01:11 2020 +0200"
  },
  "committer": {
    "name": "Matthias Sohn",
    "email": "matthias.sohn@sap.com",
    "time": "Sat Jun 06 11:10:35 2020 +0200"
  },
  "message": "Add benchmark for strategies how to move a file\n\nWe can either\n- try moving the file and, in case the target directory doesn\u0027t exist,\n  handle the NoSuchFileException this raises to create the target\n  directory\n- or we always first test if the target directory exists and create it\n in case it is missing\n\nOn my Mac this yields\n\nBenchmark                                        Mode  Cnt    Score     Error  Units\nFileMoveBenchmark.moveFileToExistingDir        avgt    5  196.490 ±  15.194  us/op\nFileMoveBenchmark.moveFileToExistingDirExists  avgt    5  223.217 ±  54.816  us/op\nFileMoveBenchmark.moveFileToMissingDir         avgt    5  332.169 ±  43.871  us/op\nFileMoveBenchmark.moveFileToMissingDirExists   avgt    5  303.815 ± 137.568  us/op\n\nThis means if the target directory of the move already exists the\nfirst strategy is faster by around 25 us/op otherwise the second one\nis faster by around 30 us/op. Which one is favorable depends on the\naverage probability that the target directory exists in real world\nscenarios.\n\nChange-Id: I03653b408b859a796508dfa1471b36c65633534e\nSigned-off-by: Matthias Sohn \u003cmatthias.sohn@sap.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "d3ada22df24d487af13fe6b89ab4a1f0c79c9e68",
      "new_mode": 33188,
      "new_path": "org.eclipse.jgit.benchmarks/src/org/eclipse/jgit/benchmarks/FileMoveBenchmark.java"
    }
  ]
}