HP3000-L Archives

March 2002, Week 4

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:
Sletten Kenneth W KPWA <[log in to unmask]>
Reply To:
Sletten Kenneth W KPWA <[log in to unmask]>
Date:
Tue, 26 Mar 2002 18:05:27 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Earlier today Jeff Milolai noted:
==========================================

We have been seeing impedes on our 989/650 .....
So we are escalated with HP now, and they responded
that we should enable DSEM and PREFETCH on our
databases. I am sorry, I just don't buy this. Why
enable an option we never had on in the first place?

Well anyway, does anyone have these options enabled?
I think it might be something I want to look into.
We are an extremely large MACS shop 1300+ users and
very large databases.
==========================================

We have had both DSEM and PREFETCH enabled on our
production database on our 959-400 for a long time
now;  at least a couple years if not longer, I think.
No problems at our site; and no outstanding problems
with either of these options anywhere AFAIK (which
of course doesn't guarantee there are no problems).

The August 1997 and later versions of the TurboIMAGE
DBMS Reference Manual have a good discussion of DSEM;
and a short description of PREFETCH.  PREFETCH is
covered mostly under "Coordinating Additions to a
Database" and similar for "Deletions" in Chapter 4.

There is just one caution listed in the manual for
enabling PREFETCH:  Be sure you have "Adequate CPU
and memory resources available on your system". Just
what constitutes "adequate" and how to make that
judgement is not defined;  I guess it's left as a
YMMV exercise to the reader.  FWIW, our 959 has 1.792
GB memory, and during routine daily operations (backup
or VSTORE not in process) our memory page fault and
Disc I/O rates per second are usually down in the
noise:  Less than 10 per second for disc I/O and less
than 5 per second for page faults is common.  Of
course we normally have less than 100 concurrent Jobs
and Sessions; our peak was somewhere around 120.  So
clearly compared to 1300+ users we are tiny...

Ken Sletten
SIGImage/SQL Chair

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2