More Time Taken for Aspose Fonts Loading

Aspose.Words Product Family
1

Hi Team

We are seeing more time when we try to read the aspose fonts (50 % of the total response time of the network call ). We are reading the aspose fonts in the below way . Could you help us is there a better way to have reduce the response time .

FontSettings.getDefaultInstance().setFontsFolder(“a/b/c”, false)

2

@veera1208

Would you please share some more details like your environment information as well as application type? Also, please share some font file that you are noticing issue with. We will further proceed to assist you accordingly.

3

@asad.ali, We are using Aspose in Java 11.0.16 on Linux (RHEL 8), Words - v22.7, Imaging - v23.8. Also we are deploying the Java application in the Kubernetes as a container.

We have wide range documents that flows into our app and there is no way for us to know the Fonts that will be used by a given document, we have placed all the Fonts from C:/Windows/Fonts/ to the container and setting path of FontsFolder using FontSettings.getDefaultInstance().setFontsFolder(fontsPath, false) at app startup.

We have two use cases:

  1. Read the Word Document properly (we are setting Fonts path like mentioned above & also Field Locking field.isLocked(true); )
  2. Read the Word document like mentioned in point 1 and then converting to TIFF.

Is there anything we can do to improve performance for both the use cases please? We are stuck with this issue in PROD.

4

@hemassridhar

Looks like your cases are related to the Aspose.Words. We are moving it to respective category where you will be assisted accordingly.

5

@hemassridhar @veera1208 The question is already answered here:
https://forum.aspose.com/t/aspose-words-imaging-performance-tuning/277993