Homegrown indexes ? Depending on their precise algorithm, and if the files
and/or indexes are nearing capacity, that would make them a possible
culprit. Another tool would help, SPT (Software Performance Tool), which
can/could track CPU consumption down to intrinsic level, and thus pinpoint
an application-related issue. Now, if the files and/or indexes have not
significantly changed recently, well ... better luck next time !
All that remains to be proved and measured with the appropriate tool and
skillset, however. But at least you know where to start.
To the best of my current knowledge, SPT is no longer sold. But Lund or
other companies certainly have similar tools.
Oh, BTW, I used to be an MPE Performance Consultant, and I'm currently
available.
Christian
> -----Message d'origine-----
> De : HP-3000 Systems Discussion [mailto:[log in to unmask]] De la part
> de Gordon Montgomery
> Envoyé : lundi 26 février 2007 23:39
> À : [log in to unmask]
> Objet : [HP3000-L] RE : [HP3000-L] CPU seconds in job question
>
> Thanks for your quick responses. A little more info has been requested.
> I do have Glanceix, but I hardly ever use it. I wouldn't know where or how
> to look at the disk queue. I do have 1 gig of RAM in this system. We
> also do NOT use any database, ( Image, Allbase, Oracle etc.) most
> of our data files are flat ascii files with home grown indexes. Our
> largest and most used file contains 15,000,000 records of 128 bytes.
>
> Like I said, I know enough to be dangerous....
>
> Thanks
>
> Gordon Montgomery
> Living Scriptures, Inc.
> (801) 627-2000
> [log in to unmask]
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
