HP3000-L Archives

October 1999, Week 3

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: Native Mode KSAM
From:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Fri, 15 Oct 1999 08:49:41 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines) 
Performance gains and reduced CM-NM switching spring to mind.

I've always wanted to benchmark old KSAM vs new, but never got round to
it.......

Neil


-----Original Message-----
From: Glenn A. Mitchell [mailto:[log in to unmask]]
Sent: 15 October 1999 07:36
To: [log in to unmask]
Subject: Native Mode KSAM


I'm converting a large application from MPE/V to MPE/iX.  In addition to a
large IMAGE database, the application uses a large KSAM file.  I am
pondering whether or not I should convert it to native mode.  I think some
of the pluses include:

1.  Not having to expand it as it grows.

2.  Not having to "recover" it after a system failure

Note that this file is heavily read but only sparsely updated (about 200
write/delete transactions per day).

Are there other things I should consider in making this decision?
Performance considerations?

--
Glenn A. Mitchell  Mailto:[log in to unmask]
3GM Associates, Inc
Portland, ME  04102
207-772-9370

ATOM RSS1 RSS2