Mailing-List: contact users-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALJK9a78K1h3CT4RMprphu6j8_psFDkf9_e=4UWYtgshbsDzVw@mail.gmail.com>
References: <564574A4.2000504@gmail.com>
	<CALJK9a78K1h3CT4RMprphu6j8_psFDkf9_e=4UWYtgshbsDzVw@mail.gmail.com>
Date: Fri, 13 Nov 2015 00:28:54 -0500
Message-ID: 
 <CALJK9a6QCmxrEhyzwCCwqoLF4KZR_zpp4f+5xFzr83oLTBM6QA@mail.gmail.com>
Subject: Re: High CPU usage in FileSystemRepository.java
From: Joe Witt <joe.witt@gmail.com>
To: users@nifi.apache.org
Content-Type: text/plain; charset=UTF-8

sorry - i see now :-)

Thanks for the analysis.  Will dig in.

Joe

On Fri, Nov 13, 2015 at 12:28 AM, Joe Witt <joe.witt@gmail.com> wrote:
> Adam,
>
> Are you on a recent master build?
>
> Thanks
> Joe
>
> On Fri, Nov 13, 2015 at 12:27 AM, Adam Lamar <adamonduty@gmail.com> 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