Re: Changing NSDocument's default saving behavior

Subject: Re: Changing NSDocument's default saving behavior
From: Ross Tulloch <email@hidden>
Date: Mon, 27 Feb 2006 11:24:32 +1100
Delivered-to: email@hidden
Delivered-to: email@hidden

I tried a few informal benchmarks but found little indication there is much of a difference. I did discover though that disk I/O can be very fast on a G5. Using only Carbon file manager routines, it is possible to write out 18MB of data in 1,152 16K separate write calls and finish in a quarter of a second.

You can't assume that all the I/O is local. In your example your writing to local storage, if you had been writing to a server volume your results would be VERY different. In-fact the above example is pretty much a nightmare scenario for writing to a server volume.


Ross.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



Prev by Date:
Re: Menu Item Bindings Problem

Next by Date:
keychain secure note

Previous by thread:
Re: Changing NSDocument's default saving behavior

Next by thread:
error: initializer element is not constant???

Index(es):

Date
Thread













  
   Home
   Archives
   Terms/Conditions
   Contact
   RSS
   Lists
   About
 






Visit the Apple Store online or at retail locations.

1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2011 Apple Inc. All rights reserved.