Liquid XML Studio works by loading the documents it is working with into memory. These files are then manipulated within the application, and if necessary written back to the disk. Because of this if you attempt to load very large files into the application you can run into problem with memory and performance. Furthermore some of the features that the editors use mean that the whole document has to be processed before they can be used, this can significantly slow down the user experience when working with large files.
When dealing with XML files some of these issues can me mitigated by turning off some of the XML Editor features.
Their are 3 editor features that can be disabled to improve performance.
|When an XML file is loaded some of these features are automatically turned off if the document exceeds certain thresholds. It is possible to turn them back on using the tool bar, but this may detract from the usability of the application.|
These can be found on the XML Editor tool bar
In order to provide outlining (code folding), the whole document must be parsed at a grammatical level, all changes to the document potentially invalidate this state, so cause the whole document to need re-parsing.
Turning this off provides the biggest performance benefits
In order to provide syntax highlighting the lexical parser must have reached the point in the document you are viewing. Changes to the top of the document, affect everything below, and so invalidate the state of everything below.
Turning this off can make a large improvements to editing performance
In order to provide intellisense, the XML must be parsed to the point where you are making your changes. If this point is near the top of the file, this can be quite quick, but if you are working at the bottom of the file, then this can take some time to do, making it make your changes.
Turning this off can improve performance when working at the bottom of large files.