Strange indeed. However since you have slow throughput scenario you could try 
to see if setting the disruptor batch size to 1 works around the issue. 

Sent from Yahoo Mail for iPhone

On Monday, April 16, 2018, 1:50 AM, Simon Cooper 
<> wrote:

 <!--#yiv2540432438 _filtered #yiv2540432438 {font-family:"Cambria 
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv2540432438 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv2540432438 
#yiv2540432438 p.yiv2540432438MsoNormal, #yiv2540432438 
li.yiv2540432438MsoNormal, #yiv2540432438 div.yiv2540432438MsoNormal 
sans-serif;}#yiv2540432438 a:link, #yiv2540432438 
{color:#0563C1;text-decoration:underline;}#yiv2540432438 a:visited, 
#yiv2540432438 span.yiv2540432438MsoHyperlinkFollowed 
span.yiv2540432438EmailStyle17 {font-family:"Calibri", 
sans-serif;color:windowtext;}#yiv2540432438 .yiv2540432438MsoChpDefault 
{font-family:"Calibri", sans-serif;} _filtered #yiv2540432438 {margin:72.0pt 
72.0pt 72.0pt 72.0pt;}#yiv2540432438 div.yiv2540432438WordSection1 {}-->
We've been encountering a problem for some time now, where the storm CPU usage 
is continually going up, until it's using all the CPU on the system. This is 
despite the topology not really doing much - 1-2 tuples a second. We first 
noticed it on 1.1.0, but it has continued after upgrading to 1.2.1.
We've isolated the problem to the disruptor-flush-task-pool. Changing the size 
of the pool doesn't really seem to change things; after a couple of days of 
'idling', those threads are working all the time inside 
DisruptorQueue.ThreadLocalBatcher and DisruptorQueue.Flusher, checking 
_overflow.isEmpty() and running _batchers.values().iterator()
Has anyone else seen similar problems? Is there likely to be a slow-burning 
task proliferation issue inside DisruptorQueue?
 This message, and any files/attachments transmitted together with it, is 
intended for the use only of the person (or persons) to whom it is addressed. 
It may contain information which is confidential and/or protected by legal 
privilege. Accordingly, any dissemination, distribution, copying or use of this 
message, or any part of it or anything sent together with it, other than by 
intended recipients, may constitute a breach of civil or criminal law and is 
hereby prohibited. Unless otherwise stated, any views expressed in this message 
are those of the person sending it and not the sender's employer. No 
responsibility, legal or otherwise, of whatever nature, is accepted as to the 
accuracy of the contents of this message or for the completeness of the message 
as received. Anyone who is not the intended recipient of this message is 
advised to make no use of it and is requested to contact Featurespace Limited 
as soon as possible. Any recipient of this message who has knowledge or 
suspects that it may have been the subject of unauthorised interception or 
alteration is also requested to contact Featurespace Limited.

Reply via email to