Benchmarks #48

Closed
hrdwdmrbl opened this Issue Nov 28, 2012 · 4 comments

Comments

Projects
None yet
2 participants
@hrdwdmrbl

In my production application, I ran some benchmarks to find the fastest JSON rendering engine. I'm using RABL to render.

I ran the same test, for 6 different templates (our most used ones), with each record from our DB, 10 times each.
I ran once for yajl and once for oj. I did not perform any configuration for either.
I rant the tests on a staging machine (same config as production), from a machine in the same EC2 zone.
Results were consistent when run multiple times.
Rails was running 3.2.9, Ruby 1.9.3, Apache.

I found that yajl was faster. I wasn't expecting it to be. Is this possible/reasonable in some circumstances (every app is different)? Is there anything I else I might have missed or might want to consider before moving ahead?

Thanks.

@ohler55

This comment has been minimized.

Show comment
Hide comment
@ohler55

ohler55 Nov 29, 2012

Owner

Please give me more details on the test. I have not found a case where o.j. has been slower. I would like to make sure o.j. stays fastest.

jackquack notifications@github.com wrote:

In my production application, I ran some benchmarks to find the fastest
JSON rendering engine. I'm using RABL to render.

I ran the same test, for 6 different templates (our most used ones),
with each record from our DB, 10 times each.
I ran once for yajl and once for oj. I did not perform any
configuration for either.
I rant the tests on a staging machine (same config as production), from
a machine in the same EC2 zone.
Results were consistent when run multiple times.

I found that yajl was faster. I wasn't expecting it to be. Is this
possible/reasonable in some circumstances (every app is different)? Is
there anything I else I might have missed or might want to consider
before moving ahead?

Thanks.


Reply to this email directly or view it on GitHub:
#48

Owner

ohler55 commented Nov 29, 2012

Please give me more details on the test. I have not found a case where o.j. has been slower. I would like to make sure o.j. stays fastest.

jackquack notifications@github.com wrote:

In my production application, I ran some benchmarks to find the fastest
JSON rendering engine. I'm using RABL to render.

I ran the same test, for 6 different templates (our most used ones),
with each record from our DB, 10 times each.
I ran once for yajl and once for oj. I did not perform any
configuration for either.
I rant the tests on a staging machine (same config as production), from
a machine in the same EC2 zone.
Results were consistent when run multiple times.

I found that yajl was faster. I wasn't expecting it to be. Is this
possible/reasonable in some circumstances (every app is different)? Is
there anything I else I might have missed or might want to consider
before moving ahead?

Thanks.


Reply to this email directly or view it on GitHub:
#48

@ohler55

This comment has been minimized.

Show comment
Hide comment
@ohler55

ohler55 Dec 9, 2012

Owner

If you are interested in helping make Oj faster, please reopen the issue with some additional details.

Owner

ohler55 commented Dec 9, 2012

If you are interested in helping make Oj faster, please reopen the issue with some additional details.

@ohler55 ohler55 closed this Dec 9, 2012

@hrdwdmrbl

This comment has been minimized.

Show comment
Hide comment
@hrdwdmrbl

hrdwdmrbl Dec 10, 2012

Sorry, I never got around to making an example that I could send. I'll get to it eventually, but until then, keep the issue closed. :) I'll wake it up when I get to it. And I will eventually get to it.

Sorry, I never got around to making an example that I could send. I'll get to it eventually, but until then, keep the issue closed. :) I'll wake it up when I get to it. And I will eventually get to it.

@ohler55

This comment has been minimized.

Show comment
Hide comment
@ohler55

ohler55 Dec 10, 2012

Owner

Okay, lets reopen when you get a chance to put together a public benchmark.

Owner

ohler55 commented Dec 10, 2012

Okay, lets reopen when you get a chance to put together a public benchmark.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment