Metrics
CLASH for Storm writes metrics in order to asses the performance.
The following is a list of metrics. All of these metrics are grouped by task and component, thus for example for a Lineitem-store with parallelism 4, there are 4 measurements (one for each task) which have to be aggregated to get the entire picture.
Store metrics
Counters
clash_metric.probeTuplesReadCounterThe total number of probe tuples read during that topology’s executionclash_metric.probeMessagesReadCounterThe total number of probe messages read during that topology’s executionclash_metric.storeTuplesReadCounterThe total number of store tuples read during that topology’s executionclash_metric.storeMessagesReadCounterThe total number of store messages read during that topology’s executionclash_metric.emittedResultTuplesCounterThe total number of join result tuples sent as result of a probeclash_metric.emittedResultMessagesCounterThe total number of join result messages sent as result of a probeclash_metric.emittedDelayedResultTuplesCounterThe total number of join result tuples sent as result of a delayed storeclash_metric.emittedDelayedResultMessagesCounterThe total number of join result messages sent as result of a delayed store
Timers
clash_metric.probeTimerThe duration of a invocation of the probe functionclash_metric.storeTimerThe duration of a invocation of the store function