This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 4f043a48381c142e308824e3b7e15435a61bbb53
tree f994f692d15a0d743ad5c2d942e2944fe3ff9140
parent f4f8923cf0ef5bd31f9e98cecf4603d0c4bde296
tree f994f692d15a0d743ad5c2d942e2944fe3ff9140
parent f4f8923cf0ef5bd31f9e98cecf4603d0c4bde296
... |
... |
|












Another thing you might want to benchmark is using something like:
def #{sym} custom(Mime::#{const}) { |format| yield(format) } endIn DM we benchmarked this as faster than using &block explicitly.
There is a wycats in my railz.
Help pls.
dkubb has a great idea. Anytime that you use &block ruby makes a new Proc from the parameter, even when no block is given. This can slow you down.
Not always. http://gist.github.com/11326
We actually already do that optimisation with active record (for count, all, etc) and it did make a difference there, but as pratik mentions it’s not quite so simple.
There’s also some subtle differences between the two with some uses (have a look at the core list around september).
If the benchmarks show it faster here, let’s go for it. but it’s not ‘free performance’
Hmm, going to have to do a little research to figure out when it is better and when it is not.