Xiaofan Hu

To summary: For go-carbon, usually you can only query metrics that are already created on disk. But with `cache-scan`, you can query metrics that haven't been created on disk, but...

> what's reasonable value for realtime-index? 10, 100, 1000, more? Hi, I think a few thousands should be good enough. Unless the go-carbon instance receives new metrics in a super...

Your `scan-frequency` is "0", try going with "5m".

Hi, looks like your go-carbon instance is receiving more than 1 million data points and can't keeping up writing cache to disk. You can try increasing it: ``` [cache] #...

Maybe try increasing the `workers` in `[whisper]`. You have to check the usage and saturation level of cpu/memory/disk. If there are more memory and io bandwidth to spare, it should...

Hi @deniszh , this one is still relevant. But would have to follow this up later.

Hi @rickyari how many metrics were you trying to query? Was there any errors logged in go-carbon.log and go-carbon-access.log?

> Do we have some internal limits for metric count? @deniszh Yep, I think so. But it probably isn't the issue that @rickyari is having. I was just wondering if...

Hi James, you can check some go version of whisper tools out here: https://github.com/go-graphite/go-whisper/tree/master/cmd With standard whisper files, there is no fundamental differences between go-carbon and whisper-dump.py. The go versions...

> could you provide an upstart script which autostarts the go-app as the fileowner in case the hoster reboots the server? Script `restart.sh` is generated on server and it could...