Score:0

Graphite's carbon-cache.py cache flush interval?

bs flag

I checked the docs and conf files, but I don't see any mention of how Graphite's carbon-cache.py decides when to flush its in-RAM cache. How often does this happen, and can I control it?

Score:0
in flag

The Graphite Project documentation on carbon.conf does not cover the settings that effect write operations.
However, the carbon.conf.example on GitHub, as well as this chapter in the O'reilly book Monitoring with Graphite cover the MAX_UPDATES_PER_SECOND setting.

Limits the number of whisper update_many() calls per second, which effectively means the number of write requests sent to the disk. This is intended to prevent over-utilizing the disk and thus starving the rest of the system. When the rate of required updates exceeds this, then carbon's caching will take effect and increase the overall throughput accordingly.

Filesystem and block storage settings for write-back and write-through will also be a factor in how much is cached in memory and when it is written out to block storage. You can also call sync to force cache write to disk.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.