Why are people talking about yajl for stringify? Isn't yajl a JSON parser? >> Anyway, if you download a 20mb heavy json, and you need to parse and reencode it, yes, you're fucked (maybe)
Maybe not! That takes less than 0.8 seconds in my browser. Non blocking, streaming. Check: github.com/dscape/clarinet JSON.parse will probably take 0.2 seconds but it is blocking afaik. I wish I could say we had a easier to use wrapper on top of low level clarinet but I don't think that exists yet. Jann Horn had started a project called node-jsos (Reads node jesus) that aimed at that. Nuno Nuno On Sun, Feb 12, 2012 at 5:49 PM, Kilian C. <[email protected]>wrote: > I'm noticing that most of you (also on other similar threads) are focusing > on parsing objects. > I'm focusing instead on stringify the output of a big json. > > My goal was to avoid blocking the whole process, not to save ram or > setting up some complicated I/O piping. > > I think 99% of the time we need a JSON parse/stringify stream method, we > are working on a bad design (as me when I opened this thread). > A fast/small chunk env should be designed top to bottom imho (streamed db > apis etc). > > Anyway, if you download a 20mb heavy json, and you need to parse and > reencode it, yes, you're fucked (maybe) > I think a big structure like a 25mb one, is surely iterative (array of > objects), some parsing/matching hack is applicable then.... > True difficulties can occur when the structure is recursive, but is a > marginal case. > > On Tue, Apr 19, 2011 at 8:20 PM, Nicholas Campbell < > [email protected]> wrote: > >> @Mikeal - Right. Thanks for the clarification. >> >> @Akzhan - Aye. You can find a repo for yajl-js at >> https://github.com/polotek/yajl-js >> >> - Nick Campbell >> >> http://digitaltumbleweed.com >> >> >> On Tue, Apr 19, 2011 at 11:55 AM, Akzhan Abdulin < >> [email protected]> wrote: >> >>> May be trying to adopt YAJL? >>> >>> 2011/4/9 Kilian C. <[email protected]> >>> >>> Hi to all! >>>> >>>> is there a non blocking JSON.strongify solution? >>>> i need to encode a big amount of data... >>>> >>>> ty >>>> >>>> kilian >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "nodejs" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/nodejs?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en. >> > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
