Closed geobeau closed 5 years ago
Note: if we finish re-writing the way metrics are globbed, the disk cache can go away because graphite-web will not need it anymore :)
It's used by carbon. But we are investigating if we need something like this or not
Carbon is not supposed to use the disk cache
Le mer. 17 oct. 2018 à 10:04, Geoffrey Beausire notifications@github.com a écrit :
It's used by carbon. But we are investigating if we need something like this or not
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/criteo/biggraphite/pull/470#issuecomment-430530360, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_DA5mdhbVEe8gRFc-GzdqI9EYUc1J5ks5uluR2gaJpZM4XMxS9 .
Because it's too slow? Goal would be to have a cache that survives the restart of a process
Because it was too problematic (because of locking) and too slow (including the has
function). The workaround was to make startup work without the cache and slowly create the metrics if necessary after startup (the rate is not configurable but could be, it also probably lacks back-pressure).
Ok, thanks for the informations!
Attempt at improving disk cache and simplify the implementation.