Github user JPercivall commented on the issue:

    https://github.com/apache/nifi/pull/563
  
    @olegz @ijokarumawak I don't think "Queue Buffering Max Time" is working 
properly. I was getting super poor performance out of PutKafka and couldn't 
understand why it would take ~5 seconds for a single message to be sent. I then 
found this property and when I adjusted it lower it fixed my performance 
problems (and higher according made it worse).
    
    Looking at the property descriptor and corresponding property in Kafka 
([seach for "linger.ms"](http://kafka.apache.org/documentation.html)), I would 
expect it to batch multiple flowfiles but instead it just hung and only 
processed one flowfile per batch. Below are a couple screenshots of the 
configuration and the stats of running 3 node cluster (saw the saw phenomenon 
running primary node only and the scheduling period was "0 secs"):
    
    ![screen shot 2016-08-01 at 5 22 23 
pm](https://cloud.githubusercontent.com/assets/11302527/17309375/8d1189e0-580c-11e6-9c58-cf1a8f9bbc99.png)
    
    ![screen shot 2016-08-01 at 5 12 26 
pm](https://cloud.githubusercontent.com/assets/11302527/17309350/792e9512-580c-11e6-8d70-19233f7132e7.png)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to