Ah ya, I guess I meant the "common" sub-dir.<div><br></div><div>In any case, I think that Neil won't be comparing Racket vs something, but just measuring the performance of a piece of Racket</div><div><br></div>
<div>Jay</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 6, 2012 at 4:06 PM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Dec 6, 2012 at 2:36 PM, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>> wrote:<br>
> On Thu, Dec 6, 2012 at 3:32 PM, Neil Toronto <<a href="mailto:neil.toronto@gmail.com">neil.toronto@gmail.com</a>> wrote:<br>
>><br>
>> On 12/06/2012 02:08 PM, Sam Tobin-Hochstadt wrote:<br>
>>><br>
>>> On Thu, Dec 6, 2012 at 12:44 PM, <<a href="mailto:ntoronto@racket-lang.org">ntoronto@racket-lang.org</a>> wrote:<br>
>>>><br>
>>>><br>
>>>> | Reimplemented really simple FFI functions (e.g. mpfr-prec, mpfr-exp)<br>
>>>> to<br>
>>>> | avoid calling overhead<br>
>>><br>
>>><br>
>>> If you have meaningful benchmarks where this makes a difference, that<br>
>>> may be useful to Matthew, since he recently was working on improving<br>
>>> the FFI's code generation.<br>
>><br>
>><br>
>> I've got some benchmarks showing via timing loops that pulling a _long<br>
>> directly out of an _mpfr takes just over half the time it takes to call<br>
>> libmpfr to do it. It's enough to make me want to rewrite simple things like<br>
>> `bfnegative?' in Racket.<br>
>><br>
>> I won't, though, if Matthew has near-future Big Plans. Or Medium Plans.<br>
>><br>
>> I see we have "tests/racket/benchmarks". Should I just drop the code<br>
>> there, or is there some kind of procedure or protocol I should follow?<br>
><br>
><br>
> Generally that directory is for benchmark Racket against other languages, so<br>
> the program has to be cross-compatible. I think you are talking about a<br>
> stress test, which can be used to monitor Racket's performance against<br>
> itself in the future to catch regressions. That's in tests/racket/stress.<br>
<br>
</div>I don't think that's right about the `benchmarks` directory -- the<br>
`shootout` directory is not cross-compatible, and we have Typed Racket<br>
benchmarks that are mostly used for benchmarking TR against plain R.<br>
<span class="HOEnZb"><font color="#888888"><br>
Sam<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Jay McCarthy <<a href="mailto:jay@cs.byu.edu" target="_blank">jay@cs.byu.edu</a>><br>Assistant Professor / Brigham Young University<br><a href="http://faculty.cs.byu.edu/~jay" target="_blank">http://faculty.cs.byu.edu/~jay</a><br>
<br>"The glory of God is Intelligence" - D&C 93<br>
</div>