iphone - Persisting an NSDictionary : performance of plist vs NSData serialization -


i considering options improve scene load times in game. game built around home brewed scripting language, convenient defining scene logic , ai tidbits. currently, parse scripts when scene initialized, , of manifests in-core nsdictionaries. dictionaries 'plain vanilla' nssomethingorother, plist'able.

as mentioned, persisting these dictionaries once, , storing resulting data in resource bundle, eliminate intensive cpu requirement of parsing syntax , semantics. improvement net difference between clean parse @ scene instantiation vs reloading resulting dictionaries disk. wondering whether dictionary's recovery disk benefit (or lose), performance standpoint, being serialized/deserialized in nsdata. have time in world write-out dictionaries, 1 time operation @ end of packaging cycle game.

any thoughts ?


Comments

Popular posts from this blog

delphi - How to convert bitmaps to video? -

jasper reports - Fixed header in Excel using JasperReports -

python - ('The SQL contains 0 parameter markers, but 50 parameters were supplied', 'HY000') or TypeError: 'tuple' object is not callable -