Best Practices for Improving Oxygen XML Performance with Very Large XML Files
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
Radu
- Posts: 9683
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Best Practices for Improving Oxygen XML Performance with Very Large XML Files
Hi,
By default when you open in Oxygen a document larger than 30 MBs, it shows a large file warning:
https://www.oxygenxml.com/doc/versions/ ... ments.html
If you load it in the "Optimize loading for huge files" support, it will be loaded instantly and presented in pages of content.
In all other situations (loading with large documents support, editing XML in Author page), working with such 200MBs documents is impractical, it's slow and requires lots of internal memory allocated to Oxygen.
What does that XML document contain? Is it some sort of database of content?
What version control server are you using? Do you store it on Git? Or export it from a database server?
What do you do with the XML document? Do you need to process it entirely? Do you produce a publication from it? Do you run queries on it?
My suggestion would be indeed to create an XSLT stylesheet to split the XML document in multiple documents, then keep the smaller documents in your version control system and either process them separately or use xi:include to assemble them all in a larger XML document.
Regards,
Radu
By default when you open in Oxygen a document larger than 30 MBs, it shows a large file warning:
https://www.oxygenxml.com/doc/versions/ ... ments.html
If you load it in the "Optimize loading for huge files" support, it will be loaded instantly and presented in pages of content.
In all other situations (loading with large documents support, editing XML in Author page), working with such 200MBs documents is impractical, it's slow and requires lots of internal memory allocated to Oxygen.
What does that XML document contain? Is it some sort of database of content?
What version control server are you using? Do you store it on Git? Or export it from a database server?
What do you do with the XML document? Do you need to process it entirely? Do you produce a publication from it? Do you run queries on it?
My suggestion would be indeed to create an XSLT stylesheet to split the XML document in multiple documents, then keep the smaller documents in your version control system and either process them separately or use xi:include to assemble them all in a larger XML document.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service