Opening a document using the Document class is significantly slower in version 21.3 compared to 16.5

Aspose.Words Product Family
1

Hi,

We’ve seen a significant performance decrease when we upgrade from version 16.5 to version 21.3.
This is just simply opening a Word document by creating a new instance of Document class passing a stream. From 0.6 seconds max on version 16.5, it’s now 1.4 seconds max on version 21.3.
image.png (12.6 KB)

You can simply replicate this by opening a number of documents using the Document class and compare the results of versions 16.5 and 21.3.

Could you kindly look into this? If there are workarounds, kindly advise.

2

@sqpd,

Please upgrade to the latest (21.4) version of Aspose.Words for .NET and see how it goes on your end? In case the problem still remains, then please ZIP and attach the following resources here for testing:

  • Your simplified source Word document you are getting this problem with
  • Please also create a standalone simple Console application (source code without compilation errors) that helps us to reproduce your current problem on our end and attach it here for testing. Please do not include Aspose.Words DLL files in it to reduce the file size.

As soon as you get these pieces of information ready, we will start further investigation into your issue and provide you more information.

3

Hi,

Please see the attached sample source code.
AsposeWordPerfTest.zip (271.5 KB)

This simply tests opening a Word document via file stream.
In this test, when using version 16.6, it averages at 0.3 seconds.
However, when using version 21.7 (latest), it averages at 2.1 seconds.
Please treat all files here as highly CONFIDENTIAL.

Let me know if you need more information.

4

@sqpd,

We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-22539. We will further look into the details of this problem and will keep you updated on the status of linked issue. We apologize for your inconvenience.

5

Hi, I can see the status of the issue is ‘Closed’.
What’s the update about the issue?

6

@sqpd,

Yes, WORDSNET-22539 has now been resolved and the fix of this issue will be included in the next 21.8 version of Aspose.Words for .NET. We will inform you via this forum thread as soon as the next version containing the fix of this issue will be released during the next week.

7

The issues you have found earlier (filed as WORDSNET-22539) have been fixed in this Aspose.Words for .NET 21.8 update and this Aspose.Words for Java 21.8 update.