From: Jeff Garzik <jeff@garzik.org>
To: Colin McCabe <cmccabe@alumni.cmu.edu>
Cc: Project Hail <hail-devel@vger.kernel.org>,
Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: tabled test corpus?
Date: Fri, 05 Mar 2010 16:28:05 -0500 [thread overview]
Message-ID: <4B917765.3040706@garzik.org> (raw)
In-Reply-To: <436f52801003051315j179e7f98nc0632fba6714cac2@mail.gmail.com>
On 03/05/2010 04:15 PM, Colin McCabe wrote:
> Random thoughts:
>
> Maybe something like a freely available dictionary would work, with
> the key as the word, and the value as the definition.
>
> You could grab git commits from the Linux kernel and make the key the
> SHA, and the value the patch.
>
> There's a lot of text in Project Gutenberg. I guess you'd have to
> decide what you want your average key / value lengths to be-- I think
> most books there are longer than 16K. Maybe you could make the key
> (book, page_number).
Yeah, I am definitely looking for something much larger than 16K. S3
values can run into the gigabytes per value...
Jeff
prev parent reply other threads:[~2010-03-05 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 15:31 tabled test corpus? Jeff Garzik
2010-03-05 18:33 ` Jeff Garzik
2010-03-05 18:47 ` Fabian Deutsch
2010-03-05 21:15 ` Colin McCabe
2010-03-05 21:28 ` Jeff Garzik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B917765.3040706@garzik.org \
--to=jeff@garzik.org \
--cc=cmccabe@alumni.cmu.edu \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox