HP3000-L Archives

July 1997, Week 5

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:
Re: Sizing/Efficiency of Native Mode KSAM Fi
From:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Reply To:
Undetermined origin c/o LISTSERV administrator <[log in to unmask]>
Date:
Tue, 29 Jul 1997 15:24:55 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (13 lines) 
In article , Ewart says...

>For example, I have a program (inherited, old but working) which links
>from a KSAM file into an Image database.  The KSAM file has about 600,000
>records in it and a capacity of 690,000.  The program runs for 399 cpu
>secs for the specified selection.  If the KSAM file is then rebuilt so
>that the 600,000 now exist in a file of capacity 900,000, then the same
>selection reduces to 360 cpu secs.

If the program is run immediately after the rebuild the reduction may be just a
result of some of the KSAM file remaining in memory.  I have seen substantial
reduction in run time when the same program is repeatedly executed.

ATOM RSS1 RSS2