Hacker News Reader

oberhamsion The Birth and Death of JavaScript [video]

modern browsers support webworkers so you get "threads" but still no shared memory.

oberhamsion Web Framework Benchmarks Round 4

ah! I didn't think of it like that. That would be interesting to see... at which concurrency level the environments crap out.

oberhamsion Web Framework Benchmarks Round 4

confusing but accurate :)

The ability to script Java is one of Ringo's killer features - for this benchmark, for example, we dropped in two jars (JDBC myqlconnector & connection pooling from apachecommons) and glued them together with 10 LOC of JS.

oberhamsion Web Framework Benchmarks Round 4

I think he is too polite to say: "patch please"

oberhamsion Web Framework Benchmarks Round 4

I will test that. Should the latency stay more constant with higher concurrency? Or what am I searching for?

Looking at the res/seq we got from round4. In order of concurrency (8, 16, 32, 64, 128, 256):

nodejs (mongodb raw)

12,541 22,073 26,761 26,461 28,316 28,856

ringojs (mysql raw)

13,190 23,556 27,758 30,697 31,382 31,997

both look like they got room to grow

oberhamsion Web Framework Benchmarks Round 4

the source is available. as a first guess: if an ORM is the typical way to do it in an env then it was used.

oberhamsion Web Framework Benchmarks Round 4

If you split a single app instance onto 15 machines, you will lose some efficiency due to network communication unless those 15 instances can work isolated without any shared data (sessions). That may not be much but worst case: you have to write that inter-machine sync code.

oberhamsion Web Framework Benchmarks Round 4

I implemented the Ringo app for this benchmark and of course ran it against Node and a couple of others to see how we would perform in this neighborhood before I opened the pull request.

And since that day I've been wondering: why does NodeJs (=V8 JS engine in C) talking to MongoDB have higher response times and latency than Ringo (=Rhino JS engine on JVM) talking to MySQL. The only thing where Node beats us JVM guys seems to be the JSON response test.

oberhamsion Web Framework Benchmarks Round 4

I think you ran into your own argument: if you are very read heavy (and lots of big sites are), it's all about caching and the DB becomes irrelevant. QED really hard to get right

oberhamsion Web Framework Benchmarks Round 4

Is there no php environment with a persistent server? Are they really all doing per request startup?

oberhamsion Web Framework Benchmarks Round 4

try our RingoJs: it's JS on the JVM. Scripting Java with JavaScript.