> 2013/3/1 Marcin Deranek <[email protected]> > >> I see gaps in the graphs, so I suspect we might see the very same >> problem Łukasz reported some time ago (Subject: Carbon stats holes) >> Not sure if it's related to the frequency I use (I send metrics every >> second and gap (1 data point missing) is every ~20 seconds: this is >> only temporarily) or it's a more generic problem - this on freshly built >> 1.4.7 >> > > I think that there is no way you won't get any gaps with such low > frequency, parsing all stats and pushing them to carbon is not free. It is > done by master and there are other plugins eating master cycles, next > master cycle when master calls plugins method starts 1 second after last > cycle finished. So in practice carbon will be called not every exact > second, but a little more (1.1s or something), after a while this added > delay will manifest itself on carbon graphs. At least that's my guess. >
Hmm, the new plugin uses the stats pusher system, so it runs in a dedicated thread. Can you check if we can drop such holes ? (we have now more freedom on the frequency and the 'heavyness' [in term of codes] of the plugin) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
