Toby Thain [toby at telegraphics.com.au] wrote:
Yes, that problem is solved by RAM, and smarter
indexing :)
24GB does help :-)
In fact, it's a *perfect* illustration of how a
fast machine
can conceal
a very inefficient design! Grepping a source tree for an
identifier is
orders of magnitude more wasteful than simply using an inverted index.
If grepping the tree were a major part of what I do then I'd do
something about it. As it is, it isn't. It also doesn't affect the
end user. If I were running on a slower, less capable machine (or
over a slow network or some other constraint) then I'd have to adopt
a different approach. But none of those constraints hold so it's
simply not an issue so I've not wasted any time trying to develop
anything "better".
Antonio
arcarlini at
iee.org