Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Aspose.Words provides a wide range of features to work with documents in various formats. It is important to note that there is no limit on the maximum size of a document file that Aspose.Words can process or render. The only limitation is the amount of RAM (memory) available on your side.
Usually Aspose.Words needs several times more memory than the document size to build a model of the document in memory. For example, if your document size is 1 MB, Aspose.Words needs 10-20 MB of RAM to build its Document Object Model (DOM) in memory. The multiplier depends on the format because some formats are more compact than others. For example, DOCX is more compact than DOC and RTF, and DOC is more compact than RTF.
There is no exact way to estimate how much memory Aspose.Words actually consumes during processing any particular document file. As you may know .NET stores data in classes, each class instance uses some memory for CLR internal purposes. So any paragraph or formatted text (even it consists of one character) takes some extra memory after loading into the DOM. Moreover, the .NET garbage collector engine uses a complex algorithm to determine the best time to perform a memory collection, making it difficult to determine the real memory consumption.
Let’s consider two documents:
As you know, a lot of modern formats like DOCX, ODT, etc. are simple ZIP archives. So, we get the following calculation algorithm:
So, as you can see, there is no linear dependence on the input document size. There are many factors that can affect the required RAM size – the document format, its complexity and structure, the number of images and their format, and a lot of other factors.
Experiments with thousands of real documents shows that typically Aspose.Words requires several times more memory than the average document size to build a document model in memory and perform simple operations like conversion between flow formats, mail merge, parse, replace, and so on. Sometimes we are talking about a multiplier of 2, and sometimes 20.
More complex operations like rendering (converting to fixed page formats), updating fields, splitting page, and others, for some documents require 20 times more resources than the memory allocated by the document loaded in Aspose.Words DOM.
If your profiling results indicate a possible memory issue in Aspose.Words, please contact our Support Team and include all the diagnostic information.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.