[ https://issues.apache.org/jira/browse/NIFI-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190152#comment-15190152 ]
Michael Moser commented on NIFI-627: ------------------------------------ It turns out that ControlRate would penalize flowfiles (default 30 seconds) which was the single largest contributor to its accuracy adhering to the specified rate. > ControlRate processor does not accurately control the rate > ---------------------------------------------------------- > > Key: NIFI-627 > URL: https://issues.apache.org/jira/browse/NIFI-627 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Affects Versions: 0.1.0 > Reporter: Michael Moser > Assignee: Michael Moser > Priority: Minor > Fix For: 0.6.0 > > > Set a ControlRate processor to something like 5 KB per 1 sec. Generate flow > files that are about 300 KB in size and feed a bunch to this processor. This > should allow about 5 files through per 5 minutes. But it allows a lot more > data through than it should. The difference seems to get worse with really > low Time Duration values. And people tend to think in number of bytes per > second so the temptation to set Time Duration to 1 sec is great. > Also, if ControlRate has multiple input queues, it seems to output even more > data than it should. > This seems to be caused by the code at the beginning of ControlRate > onTrigger(). Under some conditions when the number of files that are allowed > through per Time Duration is less than 1, the Throttle is being removed from > the throttleMap while it actually still should be in use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)