> Of course generating PDF in the background won't resolve your memory > consumption problem, which is something you should work on in > parallel. As I've already said, you should track down the problem > using lower resolution, less images, trying DOMPDF, etc. >
I was using DOMPDF for a while, and found it to be horribly slow on larger PDF documents especially if they used tables in the HTML. If you are doing this work for a client who is paying money, you might consider the prince xml library http://www.princexml.com. It is not cheap $3800 USD for the server license, but it is hands down the best PDF generation tool I've played with for two significant reasons: 1. it is BLAZING fast! Where DOMPDF would sometimes take 2-3 minutes to generate a 15-20 page complex PDF, princexml will do it in seconds and not chew through all your available memory in the process 2. it has excellent CSS+XHTML support (even better than some browsers - especially with some of the CSS print options). This drastically cuts down on my development time. I can build my reports with CSS and XHTML a heck of a lot faster than I can trying to use some weird PDF commands. And you get the benefit of portability. I can serve my reports as XHTML pages, or as PDF and only have one source document/ logic. But, again... it's expensive. They have a trial version that you can play around with and it's fully functioning (just features a watermark). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
