Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B87E6200CD9 for ; Thu, 20 Jul 2017 00:44:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B6F35169DA3; Wed, 19 Jul 2017 22:44:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0FF99169DF0 for ; Thu, 20 Jul 2017 00:44:10 +0200 (CEST) Received: (qmail 79307 invoked by uid 500); 19 Jul 2017 22:44:10 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 79298 invoked by uid 99); 19 Jul 2017 22:44:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2017 22:44:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C8A98C302C for ; Wed, 19 Jul 2017 22:44:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tMsTTdgeDN1e for ; Wed, 19 Jul 2017 22:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 43FF75FBBD for ; Wed, 19 Jul 2017 22:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7BF99E0059 for ; Wed, 19 Jul 2017 22:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3267221E92 for ; Wed, 19 Jul 2017 22:44:00 +0000 (UTC) Date: Wed, 19 Jul 2017 22:44:00 +0000 (UTC) From: "Reza Motamedi (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AURORA-1939) Thermos landing (host) page reports incorrect CPU rates when it is busy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 19 Jul 2017 22:44:11 -0000 [ https://issues.apache.org/jira/browse/AURORA-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093862#comment-16093862 ] Reza Motamedi edited comment on AURORA-1939 at 7/19/17 10:43 PM: ----------------------------------------------------------------- This seems to be totally related to psutil. I contacted the developers there. https://github.com/giampaolo/psutil/issues/1110 was (Author: rezam): This seems to be totally related to psutil. I contacted the developers there. > Thermos landing (host) page reports incorrect CPU rates when it is busy > ----------------------------------------------------------------------- > > Key: AURORA-1939 > URL: https://issues.apache.org/jira/browse/AURORA-1939 > Project: Aurora > Issue Type: Bug > Reporter: Reza Motamedi > Priority: Minor > > Thermos Observer uses `psutil` to monitor resource consumption of Thermos Processes. On a busy machine, I have noticed negative CPU values when visiting the Thermos landing page. > In my test I reproduced this by starting many processes that constantly create short lived children. This indicates that in time between `process_collector_psutil` looks up the Process children and the time it calculates the CPU time the pid of the child is actually reused by another much younger process, which leads to negative CPU times. -- This message was sent by Atlassian JIRA (v6.4.14#64029)