Stavros Macrakis <macrakis at alum.mit.edu> writes:
> I haven't been following this whole thread, so please correct me if I'm
> misunderstanding something.
>
> You're saying that indexing 3MB of text takes 7 seconds, and fetching a ~1k
> block of text from a *known location *on a disk file takes 3 seconds?
> These numbers are 2 orders of magnitude off -- something is very very
> wrong. Fetching a 1k block should take << 50mS -- for that matter,
> fetching it off the *Web* should take < 200 mS.
I agree. But I think it's spending its time on a bizarrely slow (on
CMUCL) regular expression search. This was in the previous code as well,
though, so maybe it's nothing new on that machine.
Also, if 3 seconds is "a tad slow, but not terribly slow", I presume
that the machine is pretty much unusably slow at everything else! Ray?
> And I don't understand why building the index at runtime makes any
> sense at all.
(1) There is no way to portably jump to a given byte of a text stream
and output the stuff you find there. Guesses based on character
position or byte position don't work across all the lisps we claim
to support.
(2) The perl script that was compiling stuff was very slow. I was
recompiling Maxima every couple of minutes to check that my
changes didn't break things (especially when working on the build
system). Ten seconds each time watching a perl invocation.
(3) The patches now actually have support for loading up more than one
info file and (if someone writes them) other documentation
providers. I am not personally going to back-port this
functionality to a branch without the other changes that I believe
are an improvement.
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130403/14aff9db/attachment.pgp>;