1. 25 4月, 2016 2 次提交
  2. 24 4月, 2016 5 次提交
  3. 23 4月, 2016 7 次提交
  4. 21 4月, 2016 2 次提交
  5. 19 4月, 2016 3 次提交
  6. 18 4月, 2016 2 次提交
  7. 17 4月, 2016 2 次提交
  8. 16 4月, 2016 4 次提交
  9. 15 4月, 2016 2 次提交
    • B
      Merge pull request #1555 from prometheus/beorn7/cd · 096a2ef2
      Björn Rabenstein 提交于
      Checkpoint fingerprint mappings only upon shutdown
      096a2ef2
    • B
      Checkpoint fingerprint mappings only upon shutdown · a90d6453
      beorn7 提交于
      Before, we checkpointed after every newly detected fingerprint
      collision, which is not a problem as long as collisions are
      rare. However, with a sufficient number of metrics or particular
      nature of the data set, there might be a lot of collisions, all to be
      detected upon the first set of scrapes, and then the checkpointing
      after each detection will take a quite long time (it's O(n²),
      essentially).
      
      Since we are rebuilding the fingerprint mapping during crash recovery,
      the previous, very conservative approach didn't even buy us
      anything. We only ever read from the checkpoint file after a clean
      shutdown, so the only time we need to write the checkpoint file is
      during a clean shutdown.
      a90d6453
  10. 14 4月, 2016 2 次提交
  11. 13 4月, 2016 4 次提交
  12. 09 4月, 2016 2 次提交
  13. 08 4月, 2016 1 次提交
  14. 07 4月, 2016 2 次提交