Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #55101
| From | Ron Aaron <rambamist@gmail.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Moving JSON around. |
| Date | 2017-02-25 20:02 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <o8sgo4$ms5$1@dont-email.me> (permalink) |
| References | (4 earlier) <o8bupc$cbi$1@dont-email.me> <o8bvnc$fdh$1@dont-email.me> <o8c9pv$k9p$1@dont-email.me> <o8eef8$ve4$1@dont-email.me> <a1ecfad5-fcb6-46d7-8490-104b68d8ec68@googlegroups.com> |
On 25/02/2017 8:36, Julian Fondren wrote: > On Monday, February 20, 2017 at 3:57:45 AM UTC-6, Ron Aaron wrote: >> On 19/02/2017 16:25, Ron Aaron wrote: >>> So I reran the tests on the same machine (this time the Mac -- ignore my >>> previous comment about it being slower, it has a slower CPU than my >>> Linux box...) >>> >>> Anyway, the times (best of 5 runs) I recorded for parsing that huge JSON >>> file were: >>> >>> time (s) >>> 8th: 4.446 >>> perl: 5.050 >>> ruby: 6.106 >>> python: 10.327 >> >> One more: >> node: 2.449 >> >> Not surprising, particularly. > > This time, just parsing a flat array of 24 million (+1) numbers and > printing the length of the array: > > node 3.189s > perl 3.995s > json.fs 13.916s > > Early, early code. Since there was talk about streaming parsers, I > made it one - it's an FSM that considers one character at a time: Are you storing the data or just counting? What's your perl or node code? > One interesting thing that came out of this is that, although JSON has > heterogeneous containers, 8th's containers are also heterogeneous.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-18 23:37 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-19 10:07 +0200
Re: Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-19 00:35 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-19 12:12 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-19 13:17 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-19 13:33 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-19 16:25 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-20 11:57 +0200
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-20 02:03 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-20 12:56 +0200
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-21 16:18 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-22 06:39 +0200
Re: Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-24 22:36 -0800
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-25 01:50 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-25 20:02 +0200
Re: Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-25 23:13 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-26 10:13 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-26 13:01 +0200
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-26 16:05 +0200
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-19 01:05 -0800
Re: Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-19 01:17 -0800
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-19 01:38 -0800
Re: Moving JSON around. franck.bensusan@gmail.com - 2017-02-19 16:08 -0800
Re: Moving JSON around. Paul Rubin <no.email@nospam.invalid> - 2017-02-19 17:16 -0800
Re: Moving JSON around. Julian Fondren <julian.fondren@gmail.com> - 2017-02-19 17:52 -0800
Re: Moving JSON around. Ron Aaron <rambamist@gmail.com> - 2017-02-20 07:26 +0200
Re: Moving JSON around. franck.bensusan@gmail.com - 2017-02-20 03:01 -0800
csiph-web