benchmark range-select: add benchmark result

mruby enabled range select is faster than mruby disabled range select
even when the number of records is 1000. It means that mruby query
optimizer overhead is smaller than operation time
of "between(X, 0, 'exclude', 100, 'include')" - "X > 0 && X <= 100".

Yay.