Re: [Xsltforms-support] xsltforms Performance
Brought to you by:
alain-couthures
From: Christopher D. <cd...@vi...> - 2010-01-26 16:13:08
|
I have found a partial workaround for the time being. I was able to significantly improve the performance in IE6/8 by reducing the number of elements and attributes in the instance data. The net effect was that my documents now load in about 4 seconds. This is not an ideal situation as the number of data elements in my repeat structures grow, I will be back where I started. Alain, were you able to get anything from the documents I sent you? Thanks From: COUTHURES Alain [mailto:ala...@ag...] Sent: Saturday, January 23, 2010 11:16 AM To: Christopher Dedels Cc: xsl...@li... Subject: Re: [Xsltforms-support] xsltforms Performance Christopher, I have been using xsltforms to create some complicated interfaces. xsltforms performance appears to degrade significantly as the size of the instance data increases. It does not seem to be impacted as significantly by the number of input controls on the page. This means that paging the items in my repeat element has almost no performance impact. Can you send me a link or the XForms document itself with its data ? Profiling tools report at least 13 seconds in IE 8 (2.5 seconds in FF/Chrome) Yes, IE is still very slower... to "tab" from one field to the next, regardless of whether the data in the field was changed. It's a good situation to check with a javascript debugger (focus is lost,...). As you can expect, this is not acceptable for my users. There are different possibilities of optimization in XSLTForms: less generated HTML elements, less Javascript instructions executed,... Because this has not been done yet, I hope that a minimal effort could improve it significantly. What are the scalability limits of xsltforms? This is not yet determined but there are many parameters involved: complexity, instance size, number of bindings, ... Do you have any suggestions on how to improve performance in my xforms document? Use of // in XPath expressions is surely to avoid. -Alain |