Closed rju closed 1 week ago
author André van Hoorn -- Tue, 12 Mar 2013 10:41:32 +0100
See also KIEKER-913 Done (timer plugin)
author Jan Waller -- Tue, 6 Aug 2013 17:11:01 +0200
We should use the TimeReader ( KIEKER-913 Done ) for this.
We have to be careful (currently the filter does two functions: 1) throughput during analysis and 2) throughput during monitoring)
For 2) the current approach is fine.
For 1) and for online analysis (e.g., Xing) we should use the timeReader
In this case it should replace the current mechanism.
The current input port just collects, and a new timer input port counts on intervals.
We should perhaps split the filter for 1) and 2) ?
author Jan Waller -- Tue, 10 Sep 2013 12:56:42 +0200
As a first step, I added a filter for the analysis throughput in 8059acf4dbd4897fd52a1985a27cb753ba6c783a
author Jan Waller -- Tue, 17 Sep 2013 15:49:47 +0200
This is implemented for the AnalysisThroughputFilter.
Not really practical for the MonitoringThroughputFilter.
JIRA Issue: KIEKER-1055 CountingThroughputFilter: Support for asynchronous mode Original Reporter: Andre van Hoorn
Currently, the filter is synchronous in that output is produced only after an input event was received. Especially if no event occurs within in interval a count of zero is not reported. We could extend the filter in two ways:
1. Enable a periodic timer after the first event was received and report the count of the past interval
1. Add an input for timer triggers to be generated by an external source (e.g., a timer plugin).
See also KIEKER-589 Done