Adam, What version of Java are you running?
Do you have the following lines from conf/bootstrap.conf uncommented, or are they still commented out? java.arg.7=-XX:ReservedCodeCacheSize=256m java.arg.8=-XX:CodeCacheFlushingMinimumFreeSpace=10m java.arg.9=-XX:+UseCodeCacheFlushing java.arg.11=-XX:PermSize=128M java.arg.12=-XX:MaxPermSize=128M Thanks -Mark > On Nov 13, 2015, at 12:28 AM, Joe Witt <[email protected]> wrote: > > sorry - i see now :-) > > Thanks for the analysis. Will dig in. > > Joe > > On Fri, Nov 13, 2015 at 12:28 AM, Joe Witt <[email protected]> wrote: >> Adam, >> >> Are you on a recent master build? >> >> Thanks >> Joe >> >> On Fri, Nov 13, 2015 at 12:27 AM, Adam Lamar <[email protected]> wrote: >>> Hi everybody! >>> >>> I'm following up from my previous thread about high CPU usage in GetSQS. I >>> ran into high CPU usage while developing a patch for that processor, and >>> while investigating with "top", I noticed one NiFi thread in particular >>> showed high CPU usage, even after turning off all processors and restarting >>> NiFi. >>> >>> A jstack showed this thread was busy at FileSystemRepository.java line 1287 >>> [1]. Since that is a continue statement, it suggests that the thread was >>> churning in the surrounding for loop. >>> >>> I didn't debug any further, but I did add a sleep statement just before the >>> continue, and CPU usage dropped wildly, settling around 2-4%. >>> >>> I hope this is useful information, and I'm happy to debug further if needed. >>> >>> Cheers, >>> Adam >>> >>> [1] >>> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/FileSystemRepository.java#L1287
