← Back to team overview

launchpad-dev team mailing list archive

Re: js timeout issues on ec2 due to deep js namespaces


On 09/20/2012 01:19 PM, Gavin Panella wrote:
> On 20 September 2012 15:26, Deryck Hodge <deryck.hodge@xxxxxxxxxxxxx> wrote:
>> I think the general guideline should be: "Anything more than 3 levels
>> deep should raise a red flag in review."
> This seems sensible, especially given the demonstrated performance of
> IE. It might not be a first class citizen of Launchpad (or is it? I
> can't remember) but I suspect that it's significant.

IE users often do not know they have a slow browser. When they buy a new
computer, they attribute the speed up to the hardware or the OS.

As of May, IE 8 and 9 can use launchpad to do everything (many features
were broken by our novice efforts to use YUI3). They don't have a fast
experience, but they can at least use JS to manage bugs, subscriptions,
etc.. The only code we specifically have for IE is lp.get_url_path which
is needed to page through bug listing.

>> As for profiling, I have no idea how to profile in html5-browser.
>> Maybe Curtis has ideas?  If you just need some peace of mind that
>> member resolution is really a cause for concern, we could do a test in
>> FF and Chrome using their profiler tools.  Also, "High Performance
>> JavaScript" has a great chapter on all this, if you haven't read that
>> book yet.
> I haven't; I'll see about getting/borrowing a copy.

You can run it in a lucid container or ec2. I am reminded that I wanted
to restore the option to show a window so that developer can see and
debug what is happening in the test browser.

Curtis Hovey

Attachment: signature.asc
Description: OpenPGP digital signature