Since the programmer was seeking block mode access I reasoned that he had
tried all the below already and was searching for the next level of nirvana.
Given such a short description, app is slow, there could be many options
which would move you up the throughput curve. That is one of the reasons I
like the 3000 and MPE, many resourceful and creative people out there
working to make the platform the best. And willing to share that info.

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Mike Hornsby
> Sent: Thursday, December 03, 1998 11:36 AM
> To: [log in to unmask]
> Subject: Re: HELP -FAST READ/WRITE TURBO IMAGE ACCESS
>
>
> James Wrote:
> >There are two ways of speeding up Image access that I know of;
> ><<snip>>
> >1) autodefer on <<snip>>
>
>   ( note I don't like to enable for autodefer but rather like to call
> DBcontrol Mode 1)
>
> >2) Block mode access to the DB. <<snip>>
>
> I would like to add:
> 3) use creator (;) access and * lists if possible
> 4) for details use HWMPUT or serial repack (don't add on delete
> space chain)
> 5) for masters check for bad capacity selection/fullness using
> DBloadng/HowMessy
> 6) if updating details use DBupdate and CIUPDATE in place of
> DBdelete/DBput
> 7) check pathing of discs (HPIB and SCSI are slow interfaces, more than 3
> per controller usually is too many.
> 8) put in as much memory as is physically possible or affordable
>
> A great tool combination that can help IO tuning is available at
> http://www.allegro.com/software/
> I have used syslog and filerpt on hundreds of HP3000s to identify and then
> tune the heavily accessed files. SOMETIMES THE HEAVY HITTERS ARE QUITE
> INTERESTING!
>
> Mike Hornsby
> [log in to unmask]
>