Performance issues
- 8 replies.
- This is not yet resolved.
- This question was started by Huub.
- Last post by Sjoerd Visscher.
|
user
April 29th 2009
|
Hi,
I am investigating your local host trial version Xopus 3.2.18 and have a few questions about the performance of your editor. 1. After copy/paste the content of your simple demo, till about 100kb size of the document.xml, the editor becomes significant slow, and you'll have to wait for each typing while editing the content. Can you confirm this, or is this behavior not normal? 2. What can I do to improve the editor performance for xml fragments up to, say 1MB, without loading those fragments into smaller parts, so that the editor will be fast enough for users to be able to edit those fragments normally? Regards, Huub Bonarius |
|
Xopus Team
April 29th 2009
|
Performance with large XML files becomes slow because of the large amount of HTML in the output of the editor (this is the output of the transformation by the XSL), and the fact that Xopus has to compare this output to new output when new elements are added. This is a known issue.
Loading a file of 1Mb, or larger, is perfectly possible, but having it in one view becomes a problem. It is not necessary to cut the XML up into smaller fragments, but with files like this it does become necessary to draw it in smaller parts. We've built successful implementations this way that use a 'current node' parameter to draw only a smaller fragment of a large document, for example a section of a larger document at a time. This is then drawn in conjunction with a table of contents to allow the user to navigate between sections. The performance gain is therefore in the XSL used. Some performance can also be gained from having well-written schema's where complexTypes are re-used for similar elements. |
|
anonymous user
June 9th 2009
|
I've got the same problem : large XML files (5 to 10 Mo). I work on IE6.
My xsl display small parts of the content and when the large file is loaded, i haven't got any problem to navigate through it. The problem is on load : it takes about 12 minutes to load. Why ? Is there a way to reduce this time ? Thanks in advance for your answer, Vincent Biragnet |
|
Xopus Team
June 10th 2009
|
Load times can be slow for two reasons. With a large XML file it is probably the validation that is executed on load. This can be turned off, which means that nodes are validated as you touch them in the editor. You can find this configuration feature in the local configuration, or by searching this website for validateOnLoad.
The other reason can be that the schema is complex. Twelve minutes sounds a bit much, but every possible schema state is calculated by Xopus when the schema is loaded. A model is built by which validation is done. Using more complexTypes for similar things can make that faster. I hope this is of use to you. |
|
member
June 10th 2009
|
Thanks for your answer.
Here is the detailled issue, I think i miss something : 1) xopus 3.2.19 / IE6 2) Here is my xml island in my start.html : <div xopus="true" autostart="true"> <xml> <x:config xmlns:x="http:/ <x:javascript src=".....js"/> <x:pipeline xml="myLargeFile.xml" xsd="....../schema.xsd"> <x:view name="Vue standard"> <x:transform xsl="......../stylesheet.xsl"/> </x:view> <x:view name="Vue XML"> <x:treeTransform/> </x:view> </x:pipeline> <x:validation> <x:validateOnLoad>false</x:validateOnLoad> <x:validateSimpleTypes>false</x:validateSimpleTypes> </x:validation> <x:advanced> <x:subCanvasMode>true</x:subCanvasMode> </x:advanced> </x:config> </xml> </div> I try a "medium size" xml file (about 700ko). Loading time is ok : about 20s. Navigation in the file is perfect. I try à "large size" (about 6Mo). Loading time is still very long (more than 10 minutes), navigation is still perfect. My conclusions : If it is a schema issue (the second reason you mention), the loading time should be the same in both cases. So it's probably a validation issue (first reason you mention) but i've got <x:validateOnLoad>false</x:validateOnLoad> in my configuration. Is this an IE6 issue ? Am i declaring something wrong in my xml island ? Thanks again for your answer, Vincent |
|
Xopus Team
June 10th 2009
|
Hi,
Sorry, Carl didn't know that validateOnLoad has been ignored for a while now. And it probably isn't the problem, validation is done by MSXML, which should have no problem with 5 to 10 Mb files. Probably there's not much you can do about it, Xopus is a Javascript application, and the way it is currently built, we need to traverse the whole document once at start-up. However, I would expect the time to grow linearly, but apparently increasing the document size 10 times, increases the time at least 30 times. So could you run the reproducer (Ctrl+Alt+R) in Xopus so we can take a look at your documents. If possible once for the medium size and once for the large size. Thanks, Sjoerd |
|
member
September 30th 2009
|
Apparently there is now a Chrome Frame plug in for IE that uses Chrome's much better Javascript processor to speed things up by one or more orders of magnitude. This might improve performance for validation - see google.com/chrome/chromeframe
|
|
member
September 30th 2009
|
ooops the url is http:/
|
|
Xopus Team
September 30th 2009
|
Except for the problem that Xopus doesn't support Chrome yet, but we're working on that.
|
- Support
- › Forum
- › General Discussion
- › Performance issues
React
Write a comment