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

Free Support Forum - aspose.com

Slow inital conversion

Aspose.Words Product Family
#1

Hi chaps, I have an odd problem. When you do a fresh boot to windows, if i run a conversion with Aspose.words the file can take up to 20seconds to convert.

It’s slow on first run of the Save method, we are saving to html.

After the first file all other conversions are ok, nice and fast.

Even if aspose.words is shut down, it will still be fast, it is only slow on the initial conversion.

Any ideas?

Thanks

Brian

#2

Hi Brian,

Thanks for your inquiry. I would suggest you please upgrade to the latest version of Aspose.Words i.e. v11.2.0 and let us know how it goes on your side. I hope, this will help.

Moreover, if the problem still remains, could you please attach your input documents here for testing? I will investigate the issue on my side and provide you more information.

Best Regards,

#3

Hi Awais, we tried the latest version today, and no change.

Also it happens with any word file, not a specific one.

I know these problems are tricky to diagnose, not sure what info to give you.

Brian

#4

Hi Brian,

Thanks for your inquiry.

The extra time taken on the initial conversion is probably due to the following reasons:

  • When converting to HTML often shapes and some other drawing objects are rendered to graphics.
  • The first time a page or shape is rendered, Aspose.Words needs to precache fonts and other resources for rendering. This only happens for the first conversion.

If you want to do this precaching earlier then you can simply call doc.UpdatePageLayout() on an empty document.

Could you please verify if this happens on your machine even if you are converting a document with no shapes or images and just plain text?

Thanks,

#5

Hi I was wondering is there any way to skip this precaching?

The problem we have is that we are calling aspose in a command line application.

For every file being converted to html aspose is opening and closing, as you can imagine this can be quite slow.

Do you have any suggestions on how we might speed up the initial aspose loading? We are also looking into running it as a service.

Thanks

Brian

#6

Hi Brian,

Thanks for your inquiry. To ensure a timely and accurate response please supply us with the following information, if you cannot supply us with this information we will not be able to investigate your issue and raise a ticket.

  • What version of Aspose.Words for .NET are you using?
  • What environment are you running on?
    • OS (Windows Version or Linux Version)
    • Architecture (32 / 64 bit)
    • .NET Framework version
    • Any Third Party Libraries / SDK in addition to Aspose Products
  • Please supply us with the code from your application that is causing the issue or perhaps attach your sample console application
  • Please supply us with the input Word document that is causing the issue
  • Please supply us with the output HTML that is produced by Aspose.Words

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

Many thanks,

#7

I am running the latest version on .net words on a windows 64 server. I don’t see the relevance of supplying you with test files and it happens with any files.

The question is how to speed up the initial loading of aspose and is there any way to skip precaching etc to speed things up.

Brian

#8

Hi Brian,

Thanks for your inquiry.

It could be that the problem occurs because you are using digitally signed assemblies of Aspose.Words from either net2.0_AuthenticodeSigned or net3.5_ClientProfile_AuthenticodeSigned folder. Please note that digitally signed assemblies come with an Authenticode and Signed assemblies may load slower than those without Authenticode.

Also, during the first time you run a digitally signed assembly, the .NET Common Language Runtime tries to determine whether the signature is valid or not. It does so by contacting thawte or verisign servers. In case you don’t have an Internet access on the machine you’re getting this problem on, the time out or delay can occur because thawte or verisign servers cannot be reached (this only happens for the first time after which the assembly is allowed to continue without any warning).

Best regards,