wp1 Posted August 17, 2002 Report Share Posted August 17, 2002 Your hardware compatibility table says the performance with a Pioneer DVR-104 (Mac OS X) is poor because Retrospect has to flush the buffer for each write due to deficiencies in the drive. Exactly what is "poor performance". I found one report claiming 78 MB/min (full DVD 1x). However, I've found a couple of unsubstantiated references to under 10MB/min, which isn't poor - it's abysmal. Is this report accurate? Does this apply to all levels of firmware on the 104? What about on the retail drive (which isn't listed as supported). Why does Retrospect have to flush the buffer after every write? Toast doesn't when it is writing a DVD. Is this something unique to packet writing? Link to comment Share on other sites More sharing options...
Guest Posted August 19, 2002 Report Share Posted August 19, 2002 Retrospect doesn't do the flushing; the drive needs to do this when it's writing in packet-writing mode. (Yes, it's specific to packet-writing and doesn't affect disc-at-once or track-at-once performance.) Performace will vary with this drive according to the size of the files, other processes, compression and a number of other factors. Perhaps other users can chime in with their experiences. Link to comment Share on other sites More sharing options...
wp1 Posted August 22, 2002 Author Report Share Posted August 22, 2002 Come on... Give me a number. When you certified the drive, what kind of performance did you get, and using what system for a server? If you back up 4 gigs of OS 9 and OS X, how many MB/min did you get? Link to comment Share on other sites More sharing options...
Guest Posted August 22, 2002 Report Share Posted August 22, 2002 I'm sorry, but I do not have benchmarks for this drive. Link to comment Share on other sites More sharing options...
wp1 Posted August 24, 2002 Author Report Share Posted August 24, 2002 Your hardware compatibility note says: "This drive has slow performance because it does not support continuous write commands. Retrospect has to sync the cache after each write command." Obviously, whoever certified the drive observed something in regards to performance. The specifics aren't recorded somewhere that tech support people can get access to? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.