Performance Questions and a little need for some education.

[Guy Werry]

Ick!  Yes, that's an ugly situation. 
What Bob says does make a great deal of sense.

One area I personally have found useful is to create an INDEXED subfile
instead of sorting. May help address #2, although we're a Unix / C-ISAM
shop ... Life may be different in your environment.  Since reading the
indexed subfile will follow the order of the index you can eliminate
doing the sort entirely.

Guy L. Werry
Senior Systems Analyst
Hudson Bay Mining & Smelting Co., Limited. 

-----Original Message-----
From: powerh-l-bounces+guy.werry=hbms.ca at lists.sowder.com
[mailto:powerh-l-bounces+guy.werry=hbms.ca at lists.sowder.com] On Behalf
Of Bob Deskin
Sent: Tuesday, August 18, 2009 12:38 PM
To: John Stires
Cc: powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com;
powerh-l at lists.sowder.com
Subject: Re: Performance Questions and a little need for some education.

Sounds like you need to look at the "big" picture - specifically #4 in
your list. If you're continually reading the same data from the data
files and sorting it, that's a lot of redundancy. I/O is usually the
biggest time eater with PowerHouse. I suggest minimizing that first and
then look at CPU usage.

Bob



From:
John Stires <jstires at EBDS.com>
To:
"powerh-l at lists.sowder.com" <powerh-l at lists.sowder.com>
Date:
2009-08-18 01:14 PM
Subject:
Performance Questions and a little need for some education.
Sent by:
powerh-l-bounces+bob.deskin=ca.ibm.com at lists.sowder.com



Normally, I would be at the same conclusion you all offer.  Squeezing
out 
he last bit of time and resources can be a huge waste.
 
That is precisely the problem here.  Their nightly jobs run 12 to 14
hours 
and are starting run into the users coming in  the morning to work.  It 
can be an unpleasant picture.  There are so many QTP programs involved. 
One just one such job, I counted well over 65 QTP programs, most of
which 
1,000, to 3,500 or more lines of code.  It is not so much the number of 
lines of code, but the inefficiencies involved.   They, nearly, all have

very similar issues:
 
1)      Generally, deeply cascading DEFINEs
2)      Linking as many as 20 files together in one pass and then
sorting 
(Boo Hiss!) Oh yes, including several outputs and subfiles all in the
same 
request.
3)      Sorting in general in QTP
4)      Hitting the same file several times for the same data instead of

gathering the data once, putting into a subfile for later use.
 
There are other issues as well, but these are the main ones.  When you
are 
bumping up against time constraints like this, you do what you have to
do 
and seek out all of the possible ways to shave time and resources.
There 
are a lots of techniques they have used for a long time and therefore
must 
be  "good and sound".  I am trying desperately to move their thinking
into 
ways that they will be receptive to in making these processes more 
manageable, both from the maintenance and execution time stand point.
 
All of which is say, marginal gains are, indeed successes.
 
Thanks,
John-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: 'subscribe' in message body to 
powerh-l-request at lists.sowder.com
Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to 
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
Add 'site:lists.sowder.com powerh-l' to your search terms to search the 
list archive at Google.



-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: 'subscribe' in message body to
powerh-l-request at lists.sowder.com
Unsubscribe: 'unsubscribe &lt;password&gt;' in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
Add 'site:lists.sowder.com powerh-l' to your search terms to search the
list archive at Google.

The information in this e-mail and any attachments is confidential and may be subject to legal professional privilege. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorised to, and must not, read, copy, distribute, use or retain this message or any part of it.