On Thu, 1 Mar 2018 13:12:36 +0100 Karl Gerhard karl_gerh@gmx.at wrote:

Hello Morten

Hi Karl,

I'm copying the mailing list on my response, even though you didn't.

here comes the requested output. secondsPerPoint looks right to me.

$ whisper-info /var/lib/graphite/whisper/nav/devices/router1_domain_com/ports/ae3/ifInOctets.wsp maxRetention: 51840000 xFilesFactor: 0.5 aggregationMethod: last fileSize: 45568   Archive 0 retention: 604800 secondsPerPoint: 300 points: 2016 size: 24192 offset: 64

[snip]

It does indeed. I'm left with only two possible options:

1. You are losing UDP packets (as mentioned by the debugging guide)

2. You are in fact experiencing a cache saturation problem with carbon-cache, but it's somehow being masked by its reporting of negative cache numbers.

I'd try a newer version of carbon-cache if I were you, to see if that helps. If you are indeed experiencing cache saturation, a non-buggy version might expose it properly and you can take the necessary steps - such as running multiple carbon-caches or storing your Whisper files on an SSD (although I'll add, as I've done before, that we are running carbon-cache 0.9.10 in production, as upgrading to 0.9.12 gave us abysmal performance, with cache saturation on almost every installation - so even downgrading might help).

If all else fails, you should contact someone within the Graphite project. See [1] or try #graphite on Freenode.

[1] https://graphiteapp.org/