Hi,

The most common reason that causes delay in synchronously cases is not from the HTML to PDF converter, but from deadlocks held at various places either by your code, or by ASP.NET, or by your backend database engine. This is because the HTML to PDF converter will callback to your web server to request dependency resources used by your HTML page (JavaScript, CSS, images, etc). If your server side code already holds a lock that the dependency resources happen to need as well, then a deadlock would occur (since your calling code usually won't release the lock until the conversion is done, and the conversion won't be done until the dependency resources are successfully fetched). Both ASPXToPDF and MVCToPDF has code that tries to avoid this kind of issues, but they may not be able to avoid all cases. In that case merely switching from one method to another won't solve the problem. The best option is to try to comment out code/HTML block by block and see if you can find out exactly what triggered the delay. Usually it will make sense once you find out the trigger.

Thanks!

Hi,

For a simple "Hello World" it should not be slow. Please try to:

1. Run our EOPdfDemo application directly on your server (if possible) and see if that works differently;
2. Run the same conversion multiple times and see if subsequent conversions are faster than the first conversion (the first conversion will be notably slower since it has to initialize many internal data);

Also please use task manager to monitor CPU usage of all the processes in the system. Do you see any CPU spike while conversion is in progress?

Thanks!

Hi,

I can't think of any reasons that would cause such delay. How do you measure the amount of time it takes the do the conversion? Do you measure on the server side in your code or from client side browser?

Thanks