Hi Hussein, Do you have any generalized recommendations for optimizing XMLmind performance? I've still got some users complaining about the amount of time that it takes to open large documents. They're a sticky bunch, because when I try to break the document in the chunks they complain that it's too confusing and Xrefs are difficult to create, and when I allow them to keep it as a monolithic document they complain about how slowly it opens. Overall, they're never going to completely happy until everything happens instantly and without them needing to think.
However, it's a lot easier to tell them to just live with it when I'm sure that I've done everything I can, so: 1. Is there an optimal amount of memory to devote to XMLmind, and at what point is adding more a waste of resources? 2. Are there any optional features in XMLmind that can be deactivated to increase the overall speed of the app? 3. I've seen a number of references to CSS and IDs causing some performances issues if handled incorrectly; is the correct method summarized anywhere? My documents are extremely ID-heavy due to extensive Xrefs. 4. Is there a way of shorting the initial startup time of the application? This is something that even some of our DITA users occasionally complain about, but overall it's small issue. Any other recommendations would be welcome. Predictably, the root of the problem is large (+600 pages) Docbook files. Cheers, Jeff. -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
