From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] General Question: 9fans.mbox archive and problem solving w/computers
Date: Fri, 6 Jul 2007 12:01:53 -0400 [thread overview]
Message-ID: <1cfba402c4baec643b9a3e345744c255@coraid.com> (raw)
In-Reply-To: <f7a17801342b786239d0a0ccbfcd924c@comcast.net>
most machines these days have 10x that much memory. it should
be speedy enough to use strstr(2) once you've loaded them into
memory. and even loading them into memory should take no
more than a few seconds at 80MB/s.
a more elegant solution would be to reduce each document to
a set of stemmed words, enumerate the set of all stems in all
documents and create a bit array mapping stems to message #.
but that seems like too much work for only 150MB.
- erik
prev parent reply other threads:[~2007-07-06 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 15:11 Gregory Pavelcak
2007-07-06 16:01 ` erik quanstrom [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=1cfba402c4baec643b9a3e345744c255@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).