Date: Sat, 3 Feb 2024 08:27:50 +0100 From: Paul Floyd <paulf2718@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Profiling applications Message-ID: <d7320937-1658-4e20-9a02-38a8bb159cdf@gmail.com> In-Reply-To: <20240202231428.7c711308@slippy> References: <efe56bdc-b4a8-4452-add3-a5b01c8a856a@app.fastmail.com> <20240202231428.7c711308@slippy>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03-02-24 08:14, Cy Schubert wrote: > Try DTrace. The DTrace book (if you can get your hands on it) is a good > source of information about profiling. Oracle (formerly Sun) has some > good resources. https://ekamperi.github.io/Geant4/dtrace.html may > provide some pointers. Brendan Gregg's (Brendan wrote DTrace) flame > FlameGraph is another option, though it displays hot PIDs, probably not > what you're looking for. > > The DTrace Tookit is in ports. There are some DTrace code samples there. > > Once you know where your app is spending its time you can add USDT > probes to allow you to capture snapshots of data structures at points > in time. DTrace is mostly a kernel profiling tool. Unless your code is already instrumented with USDTs it won't tell you much about your application, especially if it is CPU bound in userland. A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7320937-1658-4e20-9a02-38a8bb159cdf>