Poor deserialization performance about freddy

[zwaldowski]

The second one (lazy) might help some, but then you might as well just be putting syntax sugar on top of NSDictionary - you'd lose the safety of the enum. The third one might be workable (also: maybe look into one of the older ObjC ones), I can't find one quickly but it's gotta exist. The ultimate solution is the first one if you have the time to spare, but I imagine you don't.

[lyricsboy]

Silly question, but have you compared in a release build?

On Apr 18, 2015, at 13:28, Zachary Waldowski [email protected]
wrote:

The second one (lazy) might help some, but then you might as well just be
putting syntax sugar on top of NSDictionary - you'd lose the safety of the
enum. The third one might be workable (also: maybe look into one of the
older ObjC ones), I can't find one quickly but it's gotta exist. The
ultimate solution is the first one if you have the time to spare, but I
imagine you don't.

—
Reply to this email directly or view it on GitHub
#10 (comment)
.

[jgallagher]

Yeah those timings were from a release build. Ounchecked didn't help either.

On Sat, Apr 18, 2015 at 1:34 PM, Brian Hardy [email protected]
wrote:

Silly question, but have you compared in a release build?
On Apr 18, 2015, at 13:28, Zachary Waldowski [email protected]
wrote:
The second one (lazy) might help some, but then you might as well just be
putting syntax sugar on top of NSDictionary - you'd lose the safety of the
enum. The third one might be workable (also: maybe look into one of the
older ObjC ones), I can't find one quickly but it's gotta exist. The
ultimate solution is the first one if you have the time to spare, but I
imagine you don't.
—
Reply to this email directly or view it on GitHub
#10 (comment)

.

Reply to this email directly or view it on GitHub:
#10 (comment)

[mdmathias]

That is a bummer. My sense is that a decent intermediate solution would be to try to make makeJSON lazy somehow. I think a better, long term solution would be to make a pure JSON parser. I'd be happy to work on either or both.

[jgallagher]

Built #11 based off the JSON parser I started a while back. On my real project, it takes just under 0.5 seconds to parse the 1.5 MB JSON object (NSJSONSerialization is just under 0.2 seconds). That's close enough for me, at least for now.

[jgallagher]

Did a little more tuning today; down to just under .4 seconds. Frustrated that I can't get it lower, but I'm not sure what the problem is now. It's spending a fair amount of time in String.fromCStr, but all the other mechanisms I've tried for creating Strings are slower.