round5 benchmarks

[Simon Oberhammer]

I nearly missed the start for round5 (tomorrow!)

I just opened the pullrequest. What we changed:

 * Grob reminded me to set the JVM to -server and Xmx/Xms 512MB.
 * new mongodb tests by amigrave
 * [not visible in pull] ringo-sqlstore has received some general performance improvements by Grob in the area of query-parsing/caching and there should now be less temporary objects flying around (hopefully good for garbagecollector).

let's see how this round goes :)

 simon

[Philipp Naderer]

Is the production mode on for ringo? I am on vacation so I could not check this myself.

Bye
Philipp

--
You received this message because you are subscribed to the Google Groups "RingoJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ringojs+u...@googlegroups.com.
To post to this group, send email to rin...@googlegroups.com.
Visit this group at http://groups.google.com/group/ringojs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[si...@nekapuzer.at]

> Is the production mode on for ringo? I am on vacation so I could not check
> this myself.

yeah, they have been active in round4

here's the changes for r5:
https://github.com/TechEmpower/FrameworkBenchmarks/pull/277

simon

[Brian Hauer]

Hi Simon,

Thanks for the update.  Sorry for catching you off-guard with Round 5!  :)  I saw your note, and I'll try to be more clear about new tests and rounds.

[Brian Hauer]

Hi Simon,

Just a heads-up that we're running into errors with the Ringo + Mongo test at 256 concurrency with 20 queries per request in Round 5.  We have not diagnosed this further, but I wanted to get a note out to you early so that you're not surprised.  It's being displayed as a "0" but that essentially means it did not complete the test.

Have you been able to stress test Ringo + Mongo at high load on your own hardware?  I'd be interested to know if the behavior is consistent or something particular about our benchmark suite.

[Fabien Meghazi]

On Fri, May 17, 2013 at 10:44 PM, Brian Hauer <teona...@gmail.com> wrote:
>
> Hi Simon,
>
> Just a heads-up that we're running into errors with the Ringo + Mongo test at 256 concurrency with 20 queries per request in Round 5. We have not diagnosed this further, but I wanted to get a note out to you early so that you're not surprised. It's being displayed as a "0" but that essentially means it did not complete the test.

Could you be more precise about the errors you got ?

> Have you been able to stress test Ringo + Mongo at high load on your own hardware? I'd be interested to know if the behavior is consistent or something particular about our benchmark suite.

I must admin I had problems installing the framework on my vm and I
ended up making tests manually with ab but I don't recall the
concurrencies and requests # I used.

--
Fabien Meghazi

Website: http://www.amigrave.com
Email: a...@amigrave.com
IM: amig...@gmail.com

[Brian Hauer]

Hi Fabien,

I'll ask my colleague who ran the actual tests to follow up with the details.

[Fabien Meghazi]

Ok, thanks in advance. I'm sorry about those troubles.
I guess Simon won't be happy neither to hear that.
As far as I'm concerned, my mongo bench can be removed as it appear to
be broken.

[Brian Hauer]

Hi Fabien,

Okay, I've hidden Ringo + Mongo from the Round 5 results that we'll be posting shortly.  I'd like to get the problem resolved before Round 6.

[si...@nekapuzer.at]

> Ok, thanks in advance. I'm sorry about those troubles.
> I guess Simon won't be happy neither to hear that.

hehe, yeah, I regret forwarding your test without doing another testrun
;) I don't use mongo and can't be of much help getting it to perform....
or run without errors.

simon

[Simon Oberhammer]

if anyone wonders why ringo's round5 results are nearly identical to
round4 although we promised great improvements: the ringo test did not
update its dependencies (most importantly ringo-sqlstore where most
changes happend). we have that fixed for round6.