Teach the perf dashboard that fewer janks is better.

tools/perf/unit-info.json

 {
   "_description" : "This file contains info about our performance test units, used by the perf dashboard (http://chromeperf.appspot.com).",
 
   "%": {
     "improvement_direction": "down",
     "why": "Percent CPU usage. Used by cpu metric."
   },
   "bit/s": {
     "improvement_direction": "down",
     "why": "Bitrate."
@@ skipping 41 matching lines @@
     "improvement_direction": "up",
     "why": "layer_tree_host_perftest"
   },
   "frame_time": {
     "improvement_direction": "down"
   },
   "Hz": {
     "improvement_direction": "up",
     "why": "Higher frequencies are faster."
   },
+  "janks": {
+    "improvement_direction": "down",
+    "why": "Fewer janks is better."
+  },
   "kb": {
     "improvement_direction": "down",
     "why": "Synonym for KB, used in memory and io metrics."
   },
   "available_kB": {
     "improvement_direction": "up",
     "why": "kB of memory available. More memory available is better."
   },
   "KB": {
     "improvement_direction": "down",
@@ skipping 108 matching lines @@
     "improvement_direction": "down"
   },
   "us": {
     "improvement_direction": "down"
   },
   "vsyncs": {
     "improvement_direction": "down",
     "why": "Used in smoothness benchmarks. Number of vsyncs to generate a frame, never < 1.0"
   }
 }