Hi!I need to serialize some collection objects (NSDictionaries, NSSets, etc) to save them in the DB. I'm doing some performance tests based on the Chuck's book page 43 note.
I have tried with the NSPropertyListSerialization and java Serialized stuff (as instructed on the Apple's note http:// docs.info.apple.com/article.html?artnum=75173&coll=ap).
For serializing and unserializing the same dictionary 100000k times, I have:
NSData length: 667 String length: 326Property list serialization took 12272 milisecs, average 0.12272 per dict.
NSData serialization took 49137 milisecs, average 0.49137 per dict. (Note average values are in milisecs/dict, not secs/dict. There is two things here that actually amazed me: 1) String is shorter than binary by a factor of 2; 2) String is a lot faster than binary. I admit I was expecting the opposite.Facing this, I ask: string serialization is faster, shorter and human readable. Is there any dark reason why I should use binary serialization and not text?
Yours Miguel Arroz Miguel Arroz http://www.terminalapp.net http://www.ipragma.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
