You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Simon Cooper <si...@featurespace.co.uk> on 2017/04/25 13:29:55 UTC
High CPU usage when topology is 'idle'
Hi,
We're seeing a relatively high CPU usage (~25% in total) when the topology is relatively idle. We've implemented a ping stream in the topology that sends a tuple to all tasks checking they're all ok, but that is only sent once a second. Nearly all the CPU usage is spend in the kernel, and we're seeing lots of FUTEX system calls using strace. We're using the default settings for the disruptor work queue, and a spout idle sleep time of 50ms.
Is this to be expected? Is there anything we can try to lower the idle CPU usage?
Thanks,
Simon
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.
Re: High CPU usage when topology is 'idle'
Posted by Roshan Naik <ro...@hortonworks.com>.
Would you be able to attach the worker to Jprofiler and see which threads are consuming CPU most when idle in the Threads view ?
-roshan
From: Simon Cooper <si...@featurespace.co.uk>
Reply-To: "user@storm.apache.org" <us...@storm.apache.org>
Date: Tuesday, April 25, 2017 at 6:29 AM
To: "'user@storm.apache.org'" <us...@storm.apache.org>
Subject: High CPU usage when topology is 'idle'
Hi,
We're seeing a relatively high CPU usage (~25% in total) when the topology is relatively idle. We've implemented a ping stream in the topology that sends a tuple to all tasks checking they're all ok, but that is only sent once a second. Nearly all the CPU usage is spend in the kernel, and we're seeing lots of FUTEX system calls using strace. We're using the default settings for the disruptor work queue, and a spout idle sleep time of 50ms.
Is this to be expected? Is there anything we can try to lower the idle CPU usage?
Thanks,
Simon
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.