Re: Strange Performance Problems

I believe so, but have never used them nor know how to use them.

On 6/27/05, Jim Franz <franz400@xxxxxxxxxxxx> wrote:
> 
> Have you got Performance Tools product to do analysis of job as it is
> running, especially the database activity and snapshots of the job stack?
> jim
> ----- Original Message -----
> From: "Mike Wills" <koldark@xxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Monday, June 27, 2005 6:52 PM
> Subject: Re: Strange Performance Problems
> 
> 
> These "upgrade programs" are written by Lawson. Trust me, these programs 
> are
> not pretty. If I was to do this over, I would almost want to write my own
> conversion programs. This suckers are ineffient, buggy and big. One of the
> bugs did 50 million IO opperations per record... that was fixed, but how
> many more bugs like this are out there? The problem is that this is
> the onlyway to do the upgrade and are therefore at the mercy of
> Lawson. As far as
> how they work? I couldn't tell ya. Some access a sybolic link to a 
> csv-based
> physical file (don't ask, I don't know either). Others do a read from the
> old DB and appear to be a straight dump with a bit a data manipulation to
> handle the new date formated fields (still take forever to run). Still
> others appear to be a some other form of program that appear to more data
> manipulation of some sort. Trust me, I would never admit to writing these
> suckers.
> 
> So with that said, Lawson is a service-oriented company. Instead of
> providing good documentation and best practices, they expect you to hire a
> consultant to do this upgrade for you. We, of course are cheap and are
> figuring it out on our own.
> 
> As far as the system goes, I shut down anything I could that did not 
> affect
> live (Accounting says it has to be up :-( ). There was very little running
> and everything was running at 50 priority.
> 
> On 6/27/05, Jim Franz <franz400@xxxxxxxxxxxx> wrote:
> >
> > Just to throw out a few more possibilities:
> > What else is running on the machine when the test is running?
> > A complex interactive pgm could be killing your system performance.
> > or a web program chewing up cycles.... I've had some problems
> > w/Apache running cgi including sqlrpgle and sometimes the cursor
> > does not close right - i get a 64,000 page job log where sql is looping 
> -
> > other jobs just crawl.
> > or anything updating or reading the same files you are updating? The 
> fact
> > that
> > one test ran slow, but Fri & Wed were ok sounds like something else
> > going on in 1st test.
> > Are you calling other programs that used to be in memory (using return)
> > and
> > now
> > setting on LR?
> > Are you calling any clp for each record processed.
> > You mentioned a change to the conversion pgms?
> > <quote>The only major change between the two upgrades is that I upgraded
> > the
> > upgrade programs </quote> Are u saying these are someone elses 
> conversion
> > pgms and you don't know what's inside them? (be very afraid..) Do they
> > understand
> > record locking?
> > You may have to do a trace to see what is going on here. One extra call 
> to
> > another
> > program that sets on LR for a multi-million record file can kill this..
> > jim
> >
> 
> 
> --
> Mike Wills
> koldark@xxxxxxxxx
> http://mikewills.name
> Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>