We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Horrible Performance creating a Document(InputStream is)

Aspose.Words Product Family
#1

We are experiencing horrible performance when first creating either an empty Document (new Document()) or a document from a RTF string converted to a ByteArray (new Document(is, LoadOptions)).


The first hit seems to take 1-2 minutes while subsequent hits seem to work fine.

We are using:
- Tomcat8 / Java8
- AWS ElasticBeanstalk (single server)
- Aspose.Words 15.8.0 (licensed)

Locally, either running under Jetty or Tomcat8, we do not experience these problems.

UPDATE:
Running in the exact same server environment using Jetty9 works fine.
#2

Hi there,


Thanks for your inquiry. When a document is loaded into Aspose.Words DOM, it takes some time to load all resources first time. Please note that usually Aspose.Words needs few times more memory than document size to build model of the document (DOM) in memory. Usually, Aspose.Words needs 10 times more memory than the original document size to build a DOM in the memory.

It
is quite difficult to answer such questions because CPU performance and
memory usage all depend on complexity and size of the documents you are
loading/generating.

 Could you please share the time difference which an empty Document (new Document()) or a document from a RTF string converted to a ByteArray (new Document(is, LoadOptions)) take at Tomcat8/Java8 and Jetty9? Please also share at which Operating system you are testing this scenario. I will investigate the issue on my side and provide you more information on this.

#3

I can actually replicate the issue by just constructing a new Document() using the empty constructor.


In our code, right after we set the license if I call “new Document()” the system comes to a halt for at least a few seconds.

Running in Tomcat8, without special modifications, the Aspose portion of our app, narrowed down to the construction of the Document, takes a significant amount of time and with minimal load, 2-3 users it seems to bottle-neck the webapp.

Running in Jetty9, without special modification, the Aspose Words portion of our app seems to run perfectly (i will test this more today).

All we set in the load options, is the encoding and in some cases the format but again, just constructing an empty Document() has problems.

Aside from the webserver, Tomcat8 or Jetty9, the environment is exactly the same (AWS Linux). Approximately 4GB RAM, 4 core, etc. Also, it should be noted that running locally in a virtual machine (Linux Mint), the Tomcat8 environment seems to work well.


#4

Hi there,


Thanks for your inquiry.

When a document is loaded into Aspose.Words DOM, it takes some time to load all resources first time. Upon the first time, Aspose.Words initializes common static resources, for example fonts installed on the PC.

Could you please share the steps here to reproduce this issue at our end? Please
also share at which Operating system you are testing this scenario.

I have tested the scenario and have not found the shared issue. Creating empty document (new Document() ) takes time first time only. It takes 255 ms first time and for second time it takes around 50 ms at my end.

#5

I have more details.


I believe this is a problem running Aspose Words along side New Relic instrumentation. I can now replicate the issue in Jetty9 when I enable NewRelic. Disable it and it works fine.
#6

Hi there,


Thanks for sharing this detail. It would be great if you please share following detail for investigation purposes.

  • Please share some detail about ‘New Relic instrumentation’.
  • Please share what is the interaction of ‘New Relic instrumentation’ with Tomcat and Aspose.Words
  • Please share the complete detail about your system setup.
  • Please share here the steps which you are following to produce this issue.

As soon as you get these pieces of information to us we’ll start our investigation into your issue.

#7

Finally, I think I have the details - it has to do with the fact your JAR is signed and it is causing the -javaagent instrumentation strife.


If I “unsign” your JAR it works fine along-side NewRelic and properly handles any instrumentation.

NewRelic (http://www.newrelic.com) is used to monitor applications and requires using of the -javaagent to be able to instrument them at runtime. This is a fairly standard enterprise Java tool used by almost all of our clients.

To replicate the scenario you can spin up either Tomcat or Jetty using the -javaagent=newrelic.jar, create a simple JAX-RS service that does something as simple as create a new Document(), include the NewRelic.jar and yml file then call the REST service. In our case, a simple service is getting deadlocked at the point we start using any of the Aspose.Words API.
#8

Hi there,


Thanks for sharing this detail. We are setting up the same environment at our side. As soon as everything is setup, we will test the issue at our end and will post the results here for your kind reference.

#9

Hi there,


Thanks for your patience. I have tested the same scenario at Windows 8 and Ubuntu with Jdk 1.8 and newrelic. I have not found the shared issue. I have followed the same instructions shared here:
https://docs.newrelic.com/docs/agents/java-agent/installation/java-agent-manual-installation

I have attached the newrelic log file with this post for your kind reference. Please let us know if you have any more queries.