Hi devs, I noticed today that the time spent by Hudson to run all the WYSIWYG selenium tests (274) has increased from 19 to 22 minutes although the number of tests didn't change much from XE 2.4 and neither the tests' code. I wanted to know if this was caused by an increased WYSIWYG editor loading time so I did a quick profiling using Firefox 3.6.10 and Firebug 1.5.4. The WYSIWYG editor loading time (alone, excluding other artifacts on the host page) has three components: (T1) time to interpret the WYSIWYG editor JavaScript code (~530KB) (T2) time to load the edited document in the in-line frame (T3) time to load the editor plugins and to initialize the UI (menu, tool bar) It seems that (T3) is: * XE 2.4 -> 219.128ms, 26753 calls * XE 2.5 -> 242.968ms, 28282 calls Next I checked with Firebug's Net tab the page loading time. In order to test the editor alone I created a simple velocity template (wysiwyg.vm) that includes only the editor (plus the JavaScript and stylesheets needed by the editor). XE 2.4 ------ 4.35s -> WYSIWYG edit mode with SmartClient 2.47s -> WYSIWYG edit mode without SmartClient 3.4s -> xpage=wysiwyg with SmartClient 1.7s -> xpage=wysiwyg without SmartClient XE 2.5 ------ 3.9s -> WYSIWYG edit mode with SmartClient 2s -> WYSIWYG edit mode without SmartClient 3.2s -> xpage=wysiwyg with SmartClient 1.3s -> xpage=wysiwyg without SmartClient So the overall page loading time in edit mode has decreased. Also note that SmartClient adds a lot of time and it is used only for the XWiki Explorer tree.. This means the increased time spent on WYSIWYG selenium tests is caused by something else. Thanks, Marius