[bit.listserv.notis-l] Use of cached disk with Notis

RWWMAINT@MSU.BITNET (Rich Wiggins) (02/02/90)

Does anyone out there make use of disk controllers with cache on systems
running Notis?  I'm curious if time-consuming tasks such as index builds
run faster in such an environment.  (The rule of thumb is that I/Os
that move through large datasets without dwelling in one area of disk
are usually not good cache candidates.)

How about solid-state DASD?  Anybody use such devices to speed up Notis?

How about running VSE or MVS as a guest of VM/XA, with minidisk caching
in expanded storage?

If anyone is benefitting from these various giant versions of RAM disks,
it'd be interesting to learn about it.  Thanks.

/Rich Wiggins
 Michigan State U

ADLB001@MVS.MCGILL.CA (Ron Johnston) (02/03/90)

The best way to speed up NOTIS indexing jobs is to increase the
VSAM buffering.

HARRY@MARIST.BITNET (A. Harry Williams) (02/03/90)

On Fri, 2 Feb 90 08:58:19 EST Rich Wiggins said:
>How about running VSE or MVS as a guest of VM/XA, with minidisk caching
>in expanded storage?
Since the I/O will be via SIO(F) or SSCH and not DIAG, VM/XA SP2's mini
disk caching will not cache that I/O.  It also must be a 4K I/O
for it to be cached, ie it is aimed mainly at CMS I/O.  I was hoping
that this was not the case since one of our biggest I/O bottlenecks
is an index file.  I guess its time to look at 3880-23 or 3990s.
>
>If anyone is benefitting from these various giant versions of RAM disks,
>it'd be interesting to learn about it.  Thanks.
>
>/Rich Wiggins
> Michigan State U
/ahw