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

From: Henk Boom (henk at henk.ca)
Date: Sun Jun 7 12:35:41 EDT 2009

2009/6/7 Eli Barzilay <eli at barzilay.org>:
> 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.

Why not keep only the identifier and module names in the main index,
then when the user clicks on the link get the html information from a
.js file based on a hash of the name? Just from looking at the index
file it seems that this would shrink it quite a bit.


Posted on the users mailing list.