Performance Explorer (PEX) data will show that...

Carsten provided a link...

The iDoctor tools provide and much nicer GUI into the collected PEX data...

We once found a program taking 30% of our CPU (across 30K users...)

PEX was used to provide the following
"Statements that use the most CPU in BADPGM are the following:
79100, 79400, 79700, 80000, 80300, 80600.
Next busiest statements are:74700, 75200, 75700, 76200, 76800, 77,300, 78700
"

Took maybe an 1hr to fix (%trim() was being used repeatedly) during the
next scan BADPROGRAM wasn't using enough CPU to show up...

Charles




On Wed, Feb 19, 2020 at 1:12 PM Roger Harman <roger.harman@xxxxxxxxxxx>
wrote:

I haven't seen the code yet. I was hoping to get a histogram type view of
the hot spots.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

--

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Sent: Wednesday, February 19, 2020 10:13 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Profiling RPGLE programs

I normally eyeball the code, identify likely culprits and have it write to
the joblog. I iterate thru that process until I narrow down the cause.

HTH







-----Original Message-----

From: Roger Harman [mailto:roger.harman@xxxxxxxxxxx]


Sent: Wednesday, February 19, 2020 11:04 AM

To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>

Subject: Profiling RPGLE programs



I have a request from a sister division to look at (and, hopefully
improve) a program that is VERY long running - like 2 days long.



My first thought was I need to know the hot spots in the program but, in
all my years on this platform, I've never needed to profile a program.



Does anyone have any tips, a simple cheat sheet, or primer on the steps
involved?



Thanks!



Roger Harman

COMMON Certified Application Developer - ILE RPG on IBM i on Power

















--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.



Please contact support@xxxxxxxxxxxx for any subscription related
questions.



Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.