On 4 November 2014 19:22, Rob Miller <[email protected]> wrote: > On 10/18/2014 01:06 PM, Dieter Plaetinck wrote: >> >> 3) does heka leverage multi-core properly for the statsd workload >> (receiving the packets, and doing the aggregations)? >> > Not sure what you mean by "properly", but it is true that the StatsdInput, > which handles the UDP input and the parsing of the statsd string value, > runs in a different goroutine than the StatAccumInput, which handles the > aggregation, so those two tasks can run on separate cores. It would also be > possible to use a regular UDP input, implement the statsd parsing in a > decoder, and feed the stats into a StatAccumInput, which would mean the > whole job would be spread across three different goroutines. But some > testing would need to be done to see whether the benefits of spreading > those jobs across multiple cores outweigh the drawbacks of the channel > synchronization that is introduced with the use of more goroutines.
I'm interested in this too... I made a start on "de-Graphite"ing the current StatsD aggregation in a similar way - the regular UDP input, a StatsD decoder and filter for aggregating (similar functionality to the existing one, attempts percentiles, supports Sets, written in Lua). Still need to find time to throw some meaningful load at it for comparison etc tho. https://github.com/hynd/heka-tsutils-plugins
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
