RE: Using DVD-RAM drive

"The backup device performance differs from the device specifications"? 
What's that mean?

Would CPY OBJ('/qsys.lib/mylib.lib/mysavf.file') 
TODIR('/qopt/myvolid/mydir/myfile.savf') be a better performer since it's 
not using SAVE commands?

Or does it mean that if you yank it out of the iSeries and remove the part 
that does the verify and stick it in a PC you'd get better performance?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Wilt, Charles" <CWilt@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/01/2005 08:42 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Using DVD-RAM drive






Found the following in the v5r2 Performance Capabilities Reference 
(SC41-0607-08):

-Backup Rates-
DVD-RAM      .75 MB/s   Write
             2.8 MB/s   Read

Which comes out to the 45 MB/min I saw.

Da**, that is slow.  There is a note attached to the above number: "The 
iSeries uses the write/verify function of the backup device to assure the 
data integrity, so the backup device performance differs from the device 
specifications."  The use of the write/verify was noted in other 
documentation I had seen.  But the Performance Reference is the only place 
I've found that shows just how much it slows it down.

The v5r3 Performance Ref has the same numbers.




Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
> Sent: Monday, January 31, 2005 6:29 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Using DVD-RAM drive
> 
> 
> Ok,
> 
> Some more info. 
> 
> On the SAVSAVFDTA job, for a long, long time, the job showed 
> 39 milliseconds of CPU time used.
> 
> But finally, after about 70min.  The job finished, only 
> showed 1 second used of CPU time.
> 
> 
> Now, for comparison, the creation of the save file took only 
> about 5min.  The save file size ended up being just over 3 gigs. 
> 
> Is 45 MB/min correct or what?  My PC DVD burner, using an RW 
> disk with the packet writing driver InCD, does much better than that.
> 
> Charles Wilt
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
> 
> 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
> > Sent: Monday, January 31, 2005 5:12 PM
> > To: Midrange Systems Technical Discussion (E-mail)
> > Subject: Using DVD-RAM drive
> > 
> > 
> > All,
> > 
> > Trying to make use of the new DVD-RAM drive I installed over 
> > the weekend.
> > 
> > Found the INZOPT command...ran it and it completed 
> > successfully.  Doing a WRKLNK '/QOPT/*' or a WRKOPTVOL shows 
> > my newly created volume.
> > 
> > However, tried to do a SAVLIB LIB(LIB1 LIB2) and the job went 
> > into a EVTW status and never seemed to do anything.
> > The job got a locks on a bunch of objects from both 
> > libraries, but didn't seem to be using any CPU.  There was 
> > nothing in the joblog except for the save command.  But the 
> > optical path name I specified on the SAVLIB command had been 
> > created on the DVD-RAM.
> > 
> > 
> > So, I tried saving LIB1 to a save file and using SAVSAVFDTA 
> > to move it to the optical.  The job is still running and 
> > shows an OPTW status.  Again, nothing in the joblog but the 
> > save command and the job isn't using any CPU.
> > 
> > 
> > Am I doing something wrong or is everything working and the 
> > DVD-RAM is just really, really, REALLY, slow?
> > 
> > 
> > Thanks,
> > 
> > Charles Wilt
> > iSeries Systems Administrator / Developer
> > Mitsubishi Electric Automotive America
> > ph: 513-573-4343
> > fax: 513-398-1121
> > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion 
> > (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> > 
> > 
> 
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.