From nobody Thu Feb 23 18:03:03 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PN18q2Jc3z3sKBK for ; Thu, 23 Feb 2023 18:03:07 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PN18q0XgZz3rD0 for ; Thu, 23 Feb 2023 18:03:06 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x836.google.com with SMTP id w23so11752267qtn.6 for ; Thu, 23 Feb 2023 10:03:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:sender :from:to:cc:subject:date:message-id:reply-to; bh=eqHWGMHKo8KIgJR/B+f1XfV54pFNRhQs3BJkkb+5wOA=; b=IKeNlHI10bpPL6pULNZ4/r/GV36vcNN4QYvfp1tHVBFCW+Cw5kgZpPTOYyl9IwkQX0 9dyhulWn3uj9RbTwM3WbeGHIgPybQB59GtQHAu0nY/BECKxIWkcw7O2aWolkLSXJZX8g sg2sv3ZqDYP5otv2ijuW0mSDe8UGqEpgfFzifOHGz0CXdB1IOsH0PiDcjFwTcB/t8aOG kpAk1/aHQomnncXxIPDRL4wLqukkRtfnsKPodt3kAkmmn/4r3XDjXjB0SMS8VD/e5Gpu vbdJQAzGdtKJ0jSunuQjbPjB0J+qiRknNQFjbCq6xkOQlGzw5bcw0tHkv7miUwK7qGwv bGLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:sender :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=eqHWGMHKo8KIgJR/B+f1XfV54pFNRhQs3BJkkb+5wOA=; b=Ox2Svvy7bBZMWJjoIoffxaSoUEcdvac7Tf0ePZ0P7tdIzzjPMsgXk1gwKaaYR6IOca g6jNmHMtbgRQc3J4+kHhT+0x4OSfxo74rRBHp5lB+5EA7ZxztJuvwEWGl+iGP8jdzc2i iXAPxnpMFpVYy2oZ3lvx7/4/lXtBMedMYaJ9nVwMvs7pdp4x/4G1RP0GWoE0SnQC2mc4 UF4kQu6gm0i8EiWMFS7cfGKFdLAOzBXi17PI+BNHocfECrwUNBYNjRktxyXamztg0QFN 78MgepoI18kIXtA4GVvCEYW7cD7HAC/Yq9aHwbSj+tikBXy9rQZAz5NXQkaZf+yBDjBv F8wQ== X-Gm-Message-State: AO0yUKUADHlxdN05hGE+S5WJnArXc3CxaZbK2gHWXyqHfh1Ayaw8jTCh fi27TDZ/Y17DmiagAo4Jh22ERoaPcSo= X-Google-Smtp-Source: AK7set+P4iz6YPu/bHNOexe1Da/Um5Ao1FU9f9tmkfSWSbIpzh9NmdO4nog0tQFcIB1q4EpS84yrHw== X-Received: by 2002:a05:622a:11c1:b0:3bf:a719:3f87 with SMTP id n1-20020a05622a11c100b003bfa7193f87mr15320385qtk.66.1677175386184; Thu, 23 Feb 2023 10:03:06 -0800 (PST) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id cf7-20020a05622a400700b003bfa52112f9sm4862931qtb.4.2023.02.23.10.03.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Feb 2023 10:03:05 -0800 (PST) Date: Thu, 23 Feb 2023 13:03:03 -0500 From: Mark Johnston To: Nicolas Goldman Cc: freebsd-hackers@freebsd.org Subject: Re: Performance issues with custom kernel and schedgraph tool Message-ID: References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4PN18q0XgZz3rD0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Feb 23, 2023 at 09:19:36AM -0300, Nicolas Goldman wrote: > Hello everyone, > > I have recently been experiencing performance issues on my FreeBSD system, > specifically with the task scheduler. I have* modified the scheduler (*I’m > working on a short-term scheduler based on Petri Nets*)* and now see too > much idle processor time. I have tried using the schedgraph tool to analyze > the scheduler performance but I am receiving display errors. What kind of display errors? How are you collecting tracing info? There are two ways, one with dtrace and one with KTR. Might be, your modifications to the scheduler somehow changed or removed tracing events in a way that schedgraph doesn't handle? > I want to ask the community if anyone has experienced similar issues with > the FreeBSD task scheduler, and if they have any advice or solutions for > improving performance. Is there any way to use the schedgraph tool in > non-GUI mode, as I am having trouble running it on my system without a > graphical display? I believe schedgraph.py is the only available visualization tool, so you'd need to copy everything to a system with a grapical display. > Any help or suggestions would be greatly appreciated. Thank you in advance > for your assistance! > > Best regards, Nico.