HP3000-L Archives

October 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:
Jerry Fochtman <[log in to unmask]>
Reply To:
Jerry Fochtman <[log in to unmask]>
Date:
Thu, 7 Oct 1999 07:20:31 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
At 11:07 AM 10/6/1999 -0700, Stan Sieler wrote:
>Jerry writes:
>
>> The other suggestion I would like to offer is it is actually better to
>> load the file at the same time it is initially created, vs creating/saving
>> the file and then loading it.
>
>Absolutely, if not quite for the reason Jerry mentions:
>
>> If it is built/loaded during the same
>> open, NMKSAM will leave some ventilation space within its structures at
>> certain iterations.
>
>I'm not sure that it leaves ventilation holes.  The real reason it's
>faster is that the initial creation is done before the file is
>attached to the transaction manager (XM).  This means the XM overhead
>is bypassed.  If you create the file and then fill it later, the
>updates go through XM.

Yep, I'd forgotten about this attribute of the initial loading of KSAM/iX.
However, the ventilation that is also done is important to NMKSAM files
which will have a lot of new data added to them.  This ventilation feature
applies only to NMKSAM files where the ;REUSE option is specified during the
file's initial loading at creation.  It was done to aid in the search for
open entries when adding entries to the file. This is because with the
;REUSE option, KSAM begins its search for an opening at the beginning of
the data area.  While this is assisted by checking a counter at each data
block, the process still serially searches for an opening. This is why the
performance NMKSAM and even IMAGE w/b-trees will be impacted after a lot of
new data has been added, and one of the reasons why performance will many
times improve after the NMKSAM/b-tree indexes have been re-built, providing
the replacement KSAM file is loaded as the same time it is built (which is
how DBUTIL approaches the adding/re-building of indexes).

So there you have it....2 excellent reasons to load data into a NMKsam file
at the same time its created vs. building an empty file and then re-opening
it to add data.


/jf
                              _\\///_
                             (' o-o ')
___________________________ooOo_( )_OOoo____________________________________

                        Thursday, October 7th

          Today in 1935 - The Supreme Court moved from the Capitol
                          to its present building.

___________________________________Oooo_____________________________________
                            oooO  (    )
                           (    )  )  /
                            \  (   (_/
                             \_)

ATOM RSS1 RSS2