HP3000-L Archives

November 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Rick Clark <[log in to unmask]>
Reply To:
Rick Clark <[log in to unmask]>
Date:
Tue, 2 Nov 1999 07:05:28 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (50 lines)
I know that the program is segmented and it is a very large program used by
probally everyone in the firm. It wouldn't surprise me that even a few small
lines of code would cause such a headache... Once I return to the office I
plan on sitting down with the programmers and determine if that is the case...
Is there a max amount of space a program can take? Would a need to further
segment the program be required?

Rick 'On a Nation tour the month of Nov' Clark


James Clark wrote:

> Another thought to ponder is the size of the code after the lines were
> added. If this was CM code had to be segmented and if the compiler did the
> segmenting, your code could become terribly inefficient. It only takes a
> byte to really mess things up.
>
> James
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Stan Sieler
> Sent: Friday, October 29, 1999 4:19 PM
> To: [log in to unmask]
> Subject: Re: JSMAIN.PUB.SYS
>
> Rick writes:
> > What I have suggested is that we should really look at switching our
> > programs from CM to NM. There is a tremendous amount of overhead due to
> > this. Another area I think we should be looking at is the databases.
> > Maybe a good 'tweaking' or a reorganization is what they need. The
> > biggest problem is time....
>
> Ahh...CM?!  I have seen a COBOL sudden performance problem
> before, having to do with arithmetic overflow (during word->byte address
> calculations) getting silently (and correctly, if expensively) handled
> by CM COBOL runtime.  Perhaps someone who remembers more may comment.
>
> Absent that, I'd like to know: when performance is "bad", what's the
> CPU utilitization?  A cheap/easy way is to check the free CPU
> speedometer on every HP 3000:
> http://www.allegro.com/papers/dump.html#Speedometer
>
> If you're at, say, 75% or more CPU use, more memory isn't likely to help.
>
> --
> Stan Sieler                                          [log in to unmask]
> P.s.: please forgive typos/brevity,      http://www.allegro.com/sieler/
>       I'm typing left-handed for awhile.

ATOM RSS1 RSS2