Thanks for your patience. We have received response from our product team about your query. Please check the following developer’s comments. Hope this helps you.
There are tons of info about java application performance optimization, like this
It hardly depends on local environment. It can be completely different for a server that generates thousands documents 24/7 or for a local PC that generate only the one document by demand.
The simplest rule is: the first call of “new Document()” will cause to load all related classes and system buffer instantiation. The static Aspose.Words resources (document styles, fonts, border arts, etc.) are loaded lazily – only when they really needed and after loading they are cached during the session.
So the second call of “new Document()” will not cause class loading. If your JRE uses JIT the behaviour is more complex because of several intelligent levels of byte-code compilation and optimization.
Another performance option is to use all processor’s cores. If you have, for instance, 8 virtual cores and 8000 documents it is better to instantiate 8 threads that will handle 1000 document each. The result will be about 5 time faster than processing all 8000 documents in the single thread.
Also, you should have enough heap space to exclude swapping. Another very important thing – fast disks. Changing HDD to SSD can rise performance twice or even more depending on quantity of disk IO operations.