Hi, Assigning more memory to the jvm: NiFi runs on java. So you can set the max heap size to 32GB.
Change the bin\nifi.sh file to start java with the jvm flag: “–Xmx32g” The default value is lesser than 32GB. See this: http://stackoverflow.com/questions/28272923/default-xmxsize-in-java-8 Prajod From: Joe Witt [mailto:[email protected]] Sent: 07 June 2016 18:08 To: [email protected] Subject: Re: nifi memory question ** This mail has been sent from an external source ** Leslie You could update the flowfile queue swap threshold higher in such a case. That said at that size of a heap you may see undesirable GC behavior. Simply put what you saw when making tons of tiny flowfiles after a split and it causing slowness is a bug and should be fine on far smaller heaps. We can and should push those things out of the heap for large sessions like that. You should be able to use it like you did and see no perf implications. That we must fix. Mark Payne...do you recall the jira number to tackle this? Thanks Joe On Jun 7, 2016 6:23 AM, "Leslie Hartman" <[email protected]<mailto:[email protected]>> wrote: Hello: If you have a server with say 64 Gigs of memory and wanted to give 32 Gigs of memory to nifi, what options would you change? When I was splitting a large file up into a lot of smaller pieces it ran out of memory. Thank You. Leslie Hartman The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
