John, Sorry I didn't see this mention of DocRaptor earlier - we were monitoring the Heroku beta mailing list, but not the normal one.
You are correct in your interpretation of how the Heroku dyno is involved in the request to DocRaptor - it will be "busy" the entire time waiting for the pdf back from DocRaptor (that amount of time depends greatly on the size of the pdf you are producing). It is actually even worse if you use the "document_url" feature of DocRaptor (where you don't post the content for the pdf, but a link to the content for the pdf), and that url is on your Heroku app, because then DocRaptor's request back to your app consumes another dyno for a small time. You should be able to do something with Delayed Job, but unfortunately we haven't written any examples like that at the moment. If you want specific help working it out, please contact us at [email protected]. On our "planned features" list is actually asynchronous document generation - where you make the document creation request and give DocRaptor a callback url, and DocRaptor hits that callback when the document is done. Once that is implemented, it should give you a lot more flexibility for how you can deal with this particular issue. Glad you were checking out the DocRaptor addon, Michael Kuehl DocRaptor Support On Feb 27, 6:04 am, John Beynon <[email protected]> wrote: > it's not the process of PDF generation that I have concerns about as per my > original post - it's more about the technicalities on Heroku and how to > efficiently use dynos etc. > > John. -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
