On Aug 9, 10:49 am, Joran <[email protected]> wrote: > Great, thanks Raphael for your response and the link, that sort of > performance optimization would be great, considering that Rhino > provides such a simple interface into Java from Javascript, which the > others lack. V8 from what I gather does complete compilation as > opposed to JIT tracing. The complete compilation takes a little more > startup latency but has been said to be simpler. > > And thanks, the new JSON object is about twice as fast as json2.js, > and considering it's new there's still plenty of time for improvement, > it's great that we've got it. I'm using Rhino as a server-side JSON > api. The bulk of request time is spent parsing JSON from the database, > then serializing it for the client. So it is a little slow: if we > could drop to 44ms from 640ms that would be a dream. The slow JSON > parsing is also sending my CPU up to 100% and blocking other threads. > Rhino speed in general however would be fine as it is for my purposes, > a faster JSON object would be the killer win. > > Thanks for your work.
Raphael and I discussed the approach to take for JSON parsing and, as he indicated, we decided to go for the simplest approach given the time constraints of the Google Summer of Code program. I'd be happy for people to put together patches that improve performance of JSON parsing. If the regexp tokenizer is indeed the slow part of the code, perhaps the tokenizer in Rhino could be used, for example. Thanks, Norris _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
