2013/3/2 Łukasz Mierzwa <[email protected]> > So it isn't hard to make carbon "skip a beat" with such low frequency, and > it seems that at least part of reasons are out of uWSGI control (carbon > server response time). > To make it work better I think that we would need to have a thread that > only does one thing - sleeps for $(carbon freq) seconds and than creates a > new thread that will collect current metrics and push data to carbon, after > it's done or it had any problems, it dies (?). >
Or instead of creating new thread for each cycle, use a pool of threads for pushing each set of metrics. Use first available, if all are busy kill the one with oldest metrics (?). But threads are tricky, I'm not sure if it would work. -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
