Hallo Christoph, this is still not good enough ;-( I think that we need to investigate more on this.
Cheers, Marc. Christoph Witych wrote: > Dear Marc, > > performance is now better using the config you stated. Some statistics: > > Testsuite run with version/config | duration > WebTest R_1660 (HtmlUnit-1.14) | (00:13:24) > WebTest R_1705 (HtmlUnit-2.1) | (00:36:44) > WebTest R_1705 with | > HtmlUnit-2.2-SNAPSHOT no CSS | (00:23:53) > > Thanks and Cheers, > Christoph > > > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Marc Guillemot > Gesendet: Freitag, 23. Mai 2008 10:34 > An: [email protected] > Betreff: Re: [Webtest] Major performance problem after upgrading to R_1705 > > Hi Christoph, > > HtmlUnit-2.1 introduced processing of CSS "on demand" for maximal > efficiency, which means only when scripts wants to access CSS related > properties. Nevertheless in some cases, you *know* that CSS processing > doesn't matter for your tests and even the "on demand" processing is too > slow. HtmlUnit-2.2 snapshot already contains an option for this: > WebClient.setCssEnabled(true/false). You can pick a snapshot to use it > already. > > It would make sense to add a config option for this once WebTest uses > HtmlUnit-2.2. Can you open an issue for it? > > Cheers, > Marc. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
