<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><font face="Helvetica, Arial,
sans-serif">I'd just add that folks should remember that they
are posting numbers for their deduper against the /dedup-more
volume. This is due to reasons covered in a previous list
posting wherein it was discussed that (unexpectedly) the /dedup
volume is very easy to dedup if you've optimized a little... in
just a couple of seconds to be exact. So in summary, please
submit your scores for runs against /dedup-more.<br>
<br>
A call for submissions will come very soon (I'm thinking
Monday). We can't judge the contest in real time knowing that
some of these entries are going to take a while to run, and
knowing that watching progress bars doesn't make for fun online
streaming. We'd rather use that time to talk about which few
entries turned out to be the fastest and simply demo only them,
giving us enough time allowance at the end of the meeting for
open discussion and recognition of winners in all other
categories. Please get that code ready! Time is running out!<br>
<br>
Reminder: the reference code is <a
href="https://github.com/tommybutler/dupfind">here</a>, which
you are still free to fork and use as a starting point</font><font
face="Helvetica, Arial, sans-serif">.<br>
<br>
--Tommy Butler<br>
<br>
On 01/03/2014 07:45 PM, Tom Metro wrote:</font><br>
</div>
<blockquote cite="mid:52C767D1.1020306@gmail.com" type="cite">
<pre wrap="">For those of you ultra competitive types, we've set up a pre-contest
leaderboard (score board) so you can see how you score against the
competition. </pre>
</blockquote>
<font face="Helvetica, Arial, sans-serif"><snip></font><br>
<blockquote cite="mid:52C767D1.1020306@gmail.com" type="cite">
<pre wrap="">How to report your score: post your score in #dfwpm-scores on IRC (that
way other developers in the main room who don't want to be distracted by
the scores won't see them) and Tommy or I will update the leaderboard.
Reporting format should be like:
runtime: 159.134 (seconds and fractional seconds)
memory: 3234123 (bytes)
loc: 256 (lines of code)
critic: 2 (Perl::Critic score)
Omit values if they haven't changed since you last reported scores, or
for attributes you don't plan to compete on.
A different leaderboard will be used on competition day to hold the
results measured by the judges.
-Tom
</pre>
</blockquote>
<br>
</body>
</html>