Re: Shootout [ATTN: Brent W. Hughes]
Brent W. Hughes wrote:
>
> Yes, Jason, I have been lurking occasionally but I've been involved in some
> other things
> lately that have kept me away from full activity and I may have missed some
> postings.
> At any rate, let me post some thoughts on the Shootout. Maybe you folks are
> way ahead
> of me on this, but here goes anyway.
>
> I think we should not go to the official Shootout people until we have at
> least 15
> of the benchmarks implemented.
Agreed.
> I suggest we have our own mini-shootout with the contestants
> being Euphoria, C/C++, and Python (comparing us to one fast language and one
> interpreted
> language). Perhaps Rob could post a link to the results of our mini-shootout
> on the
> Euphoria home page.
Yes, it could be good advertising.
My original thought was to compare the following:
Euphoria 2.4
Euphoria 2.5 interpreted
Euphoria 2.5 translated
eu.ex interpreted
eu.ex translated
C
My thought was to use one of the C programs such as sieve as the timing standard
and rate the other contestants in those units.
When it comes to comparing to other languages, I would like to compare against
C, Python, and Qu. 
>
> To this end I would suggest having three types of people involved in our
> shootout:
> 1. A coordinator
> 2. Implementers
> 3. Testers
>
> The coordinator would maintain a list of the algorithms together with the
> names of
> those who have implemented them, or checked them out for implementing, or
> whether they're
> still up for grabs. For example:
>
> Algorithm Implementer
> =============== ===============
> Ackermann Derek Parnell
> Word-Count Jason Gade
> Sieve of Eras. Robert Craig
> Fannkuch Jason Gade*
> Harmonic ----
> Nested loops ----
> ... ... ...
> An asterisk means it is checked out but not yet completed.
>
> Implementers would "check out" algorithms from the cooridinator. When
> finished writing
> the code, the implemeners would hand it off to the coordinator (and post in on
> Euforum
> so everyone can witness the progress of the shootout and maybe encourage
> others to
> join in on the fun). The coordinator would update his list and pass the code
> off to
> the testers.
I don't think it needs to be that formal. Its not like we're writing a standard
library or anything 
I need to zip up what I have so far and put it in the archive. If someone else
writes a piece they can just send it to me and I'll add it in.
One big challenge that awaits me is how to measure the results? I installed
Linux partially for the purpose of this project, I wonder if I could get the test
framework used by the shootout people.
If not, I would write one in Euphoria.
If a test framework wouldn't work out right, then each benchmark would have to
report its own time at the end of its run.
Another thing, will all programs that run on Linux require the addition of
include dll.e
-- code
free_console()
?
<snip>
> Thoughts, anyone? Volunteers?
>
>
> Brent
>
=====================================
Too many freaks, not enough circuses.
j.
|
Not Categorized, Please Help
|
|
