From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: Profiling Ada applications using gprof
Date: Tue, 04 Dec 2018 14:41:04 -0500
Date: 2018-12-04T14:41:04-05:00 [thread overview]
Message-ID: <6cld0etrovikio6le8inketpn2i4qjmtg2@4ax.com> (raw)
In-Reply-To: 8441254e-f634-4077-b8d9-d988dab3406c@googlegroups.com
On Tue, 4 Dec 2018 07:04:40 -0800 (PST), joakimds@kth.se declaimed the
following:
>
>As one can see there is nothing that indicates that something takes around 10 seconds to execute. Is it really impossible to detect the long running entry call A.Stop?
>
Hypothesis: your profiling is showing CPU time consumed by the program,
not wall-clock time -- but your 10 second DELAY statement could be a
blocking call depending upon how the run-time interface was created (ie:
block waiting for some timer to expire) and consumes no CPU while blocked.
(And your 0.17s could be the time the system takes to load the executable.)
Change the DELAY to something that actually consumes CPU time and see
what happens.
Start_T := ada.real_time.clock;
while (Start_T + 10.0) > ada.real_time.clock loop
null;
end loop;
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
next prev parent reply other threads:[~2018-12-04 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 15:04 Profiling Ada applications using gprof joakimds
2018-12-04 19:41 ` Dennis Lee Bieber [this message]
2018-12-05 14:13 ` Petter Fryklund
2018-12-05 15:32 ` joakimds
2018-12-05 16:05 ` joakimds
2018-12-05 17:27 ` Dmitry A. Kazakov
2018-12-05 20:11 ` Dennis Lee Bieber
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox