[plt-scheme] firefox locking up 15 seconds for each plt documentation search

On Jun  7, Neil Van Dyke wrote:
> Eli Barzilay wrote at 06/07/2009 07:20 AM:
> > I'm happy to hear any other ideas people might have.
> 
> As I said, with Firebug disabled, performance is fine for me.
> 
> If the index is simply getting too big for some other browsers,
> another option is to break up the index and selectively load parts
> of it on demand.  (I'm being vague saying "load" here, because I
> don't know whether the bottleneck would be I/O or JS/GC.)  That
> would still use a normal Web browser and not require a Scheme
> server, but the implementation would be more complicated, and there
> would be latency issues compared to a browser that could keep the
> entire index loaded.

The complication would be considerable, I think -- I don't see any
obvious point where the code will decide to load the other chunks.

Another issue with this is that "load" -- I think that the way to do
that is to have JS code that dynamically add a script tag to the
header, or some similar ajaxy-ish thing, and with the amount of
headaches involved with JS running from local files, I hesitate to add
more stuff.

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                  http://www.barzilay.org/                 Maze is Life!