[
https://issues.apache.org/jira/browse/NIFI-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142171#comment-17142171
]
ASF subversion and git services commented on NIFI-7501:
-------------------------------------------------------
Commit 704260755a5de756aefc303029cf7b3dda556993 in nifi's branch
refs/heads/master from dennisjaheruddin
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7042607 ]
NIFI-7501
Update nf-context-menu.js for an intuitive road to parameters
When rightclicking a process group the variables are shown, but parameters are
not. This makes sense as they have a prerequisite, in the form of a parameter
context. This change gives a more consistent experience for finding the
functionality regarding parameters by ensuring the contextmenu shows the
possibility to configure a parameter context. Once the paramater context has
been created for a process group, the parameters text shows, so this is no
longer visible. People would then need to click configure to change the
context, just as they would be required to do now.
Added generateflowfile load tag and description
Added GenerateFlowFile load tag to be consistent with DuplicateFlowFile and
updated description to refer to DuplicateFlowFile.
Revert "Update nf-context-menu.js for an intuitive road to parameters"
This reverts commit 3c44b1661f09fb6ae11d2f088550f81fb7a4b393.
This closes #4333
Signed-off-by: Mike Thomsen <[email protected]>
> Generate Flowfile does not scale
> --------------------------------
>
> Key: NIFI-7501
> URL: https://issues.apache.org/jira/browse/NIFI-7501
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.11.4
> Reporter: Dennis Jaheruddin
> Priority: Minor
> Fix For: 1.12.0
>
> Attachments: generationperformance.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> One of the purposes of Generate Flowfile is load testing. However,
> unfortunately it often appears to become the bottleneck itself. I have found
> it not to scale well.
> Example result from my laptop:
> I want to generate messages and bring them to a single processor, lets call
> it processor X.
> With 1 concurrent task, and a batch size of 1, and a message size of 10MB and
> uniqueness false it can generate approximately 2 GB/sec.
> When allowing for more concurrent tasks, or a larger batch size, no
> noticeable change is found.
> However, if instead of increasing the batchsize I route the success
> relationship to multiple processors that do 'nothing' (like updateattribute),
> and then bring the success relations of all these to processor X, I can get
> much more than 2 GB/sec.
>
> In conclusion: I don't appear to be hitting a hardware limit as I am able to
> generate the number of messages in this inelegant way, but no matter how I
> set up my generateflowfile processor, it just will not scale. Suggesting
> there may be a smarter way to generate data when uniqueness is not required.
>
> I have attached a template to illustrate my findings.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
