3

I'm testing the SelectPdf Community Edition for a new project.

I'm converting a single-page HTML document to PDF. On my local dev machine, this takes 2-3 seconds. But when deployed to our test web server, the same conversion takes about 3.5 minutes. (The amount of time is very consistent.)

What could be causing such a slow conversion on the web server and why would it be so different from my development machine?

Doug
  • 2,400
  • 2
  • 18
  • 24
  • It appears the SelectPdf library might be creating an outbound connection while processing. This connection would be blocked by the firewall on our web server, maybe causing SelectPdf to hang while waiting for a response? – Doug Jan 04 '19 at 16:54
  • 1
    I have also noticed the performance of PDF generation is consistently slow. I assume - they are checking the license against their database. Are you looking at other alternatives? – Coder Absolute May 20 '19 at 04:58
  • 1
    I've looked but haven't found a good one yet. Let me know if you have any luck! (For the above project I was able to get away with leaving the page as HTML and adding a good print stylesheet.) – Doug May 21 '19 at 15:03
  • Just had an aswer from support: "The difference is machine power. The conversion to PDF is very CPU intensive..." – Joop Stringer Jun 01 '20 at 15:16
  • Thanks, but I'm 100% positive that CPU was not the cause. I'm convinced it was the blocked outbound connection. Using HTML and a well-crafted print stylesheet turned out to be a better solution anyway. – Doug Jun 03 '20 at 20:16

0 Answers0