• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSKeyedArchiver - alternatives for speed improvements?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSKeyedArchiver - alternatives for speed improvements?


  • Subject: Re: NSKeyedArchiver - alternatives for speed improvements?
  • From: Will Mason <email@hidden>
  • Date: Tue, 30 Aug 2005 05:55:16 -0700 (PDT)

NSArchiver performs significantly better than NSKeyedArchiver - in some
of my tests more than 100 times better. I've always just been annoyed
by NSKeyedArchiver, since sometimes it feels like I can type binary
numbers faster than it can write them.

Good luck, especially after NSArchiver becomes fully deprecated,
Will

--- Keith Blount <email@hidden> wrote:

> Hello,
>
> This is a question that has been asked before, I know,
> but my searches of the archives and CocoaDev have only
> found lots of questions and no real solution...
>
> I have an app that works a little like Xcode: it has
> an outline view that represents virtual folders and
> text files. Whenever the user adds a new text file, it
> is saved within the document's file wrapper as an RTFD
> file, and the contents of the outine view (an array of
> root-level node model objects, each of which keep an
> array of children) is saved to disk using
> NSKeyedArchiver. This way, the project is auto-saved
> each time a document is added.
>
> The problem is that - as has been noted a number of
> times - NSKeyedArchiver is *slow*. Once I have about
> 700 odd files in my project, if I click my "add
> document" button, it takes a few seconds to respond -
> because NSKeyedArchiver is taking so long to save all
> the data to disk.
>
> Is there a better way to do go about this that will be
> faster? My model object mostly contains strings and
> ints, but it also contains an NSImage, so isn't really
> suitable for property list serialization (I think -
> though I was left baffled by the documentation on
> property list serialization, I fully admit).
>
> Many thanks in advance for any suggestions,
> Keith
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>  _______________________________________________
> 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
>

 _______________________________________________
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

References: 
 >NSKeyedArchiver - alternatives for speed improvements? (From: Keith Blount <email@hidden>)

  • Prev by Date: Re: [Way Off Topic] Keychain Access question
  • Next by Date: Re: Pausing and terminating a thread
  • Previous by thread: NSKeyedArchiver - alternatives for speed improvements?
  • Next by thread: Object Identity Tests in Core Data
  • Index(es):
    • Date
    • Thread