prometheus/storage
beorn7 a90d645378 Checkpoint fingerprint mappings only upon shutdown
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.
2016-04-15 01:03:28 +02:00
..
local Checkpoint fingerprint mappings only upon shutdown 2016-04-15 01:03:28 +02:00
metric Anchor regexes in vector matching 2015-11-05 11:23:43 +01:00
remote Add missing license headers 2016-04-13 16:08:22 +02:00
storage.go Fix deadlock, structure target logging 2016-02-03 10:39:34 +01:00