graphite-dev team mailing list archive

[Nick <nleskiw@xxxxxxxxx>]

Are you getting lag on new metrics, or existing metrics?  A new metric won't graph properly until the data has been written to disk.  The you should get the union of disk & cache.

-Nick

On Dec 27, 2012, at 11:41 AM, Cody Stevens <question217749@xxxxxxxxxxxxxxxxxxxxx> wrote:

> New question #217749 on Graphite:
> https://answers.launchpad.net/graphite/+question/217749
> 
> After upgrading to 0.9.10 our graphs are lagging behind.   We have set our 
> 
> MAX_UPDATES_PER_SECOND  according to the formula  outlined in this answer https://answers.launchpad.net/graphite/+question/212303
> 
> Using the formula has made our graphite installation much more stable however we seem to have lost real time visibility.  
> 
> Now the graphs lag behind about the duration of a write cycle.  Once the datapoints in the cache are flushed to disk the graphs update.    I thought graphite pulled data both from the cache and from disk but either I misunderstood the inner workings or I have a misconfiguration somewhere.   The MAX_UPDATES_PER_SECOND value decreased significantly which is obviously buffering more into the cache.   As I stated before this has made our cache perform much more stably.  Any suggestions on what to check? 
> 
> Thanks !
> 
> 
> -- 
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to     : graphite-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help   : https://help.launchpad.net/ListHelp