Is there any guidance on minimizing the time is takes a load a caja guest
page?  The attached files demonstrate a little test case I'm using to
measure the time it takes to load and run a trivial caja guest page.
 Please let me know if there are any major issues with this methodology.

Here are samples of its output across three different browsers (all on a
2.2 GHz i7 MacBook Pro with 8GB of RAM):

  Chrome 23.0.1271.64:
    Total Time: 964ms (cold start in a new browser)
    Total Time: 740ms (after a few reloads in the same browser tab)

  Firefox 16.0.2:
    Total Time: 740ms (cold start in a new browser)
    Total Time: 762ms (after a few reloads in the same browser tab)

  Safari 6.0.2:
    Total Time: 502ms (cold start in a new browser)
    Total Time: 443ms (after a few reloads in the same browser tab)

I certainly wouldn't claim that this a valid full-blown benchmark.  But it
does seem to give a general indication of the startup overhead for a caja
guest on various browsers.

Are there any general practices that can be used to minimize this overhead?
 Has anyone done more extensive tests along these lines?  And if so, did
those tests produce similar results (such as the significantly better guest
page load times on Safari versus Chrome or Firefox)?

Thanks,
Jamey

container.html < 1K Download

guest.html < 1K Download

(Note that forceES5Mode is intended for debugging/testing purposes only and
if set to true may cause insecurity. You should never use it in a public
application. Its relative "es5Mode" is safer, if you must have a flag.)

Thanks, Kevin.

The reason I did that is that I'm not clear on how functional and
production-ready ES5 mode really is.  When will it no longer be label as
Experimental?

As one specific example, does it support external javascript library
references?  When I change the little test case to use jquery (per the
attached files), it stops working in Safari 6.  Is that expected at this
point?

Thanks,
Jamey

container_jquery.html < 1K Download

guest_jquery.html < 1K Download