Thanks for the fast reply.
Thomas Hoevel wrote:
The usual: faster CPU, more RAM, faster SSD, …
this program is being run on a azure server, there isn't really any margin for us to improve the server as of now.
Thomas Hoevel wrote:
Maybe it helps to have more, but smaller tables. Maybe one table per months instead of one table for the whole year, if that is applicable.
This could be achieved, but have you tested this before or is there a reason why more tables would be faster?
Thomas Hoevel wrote:
Maybe create RTF and use Word to create the PDF.
Does this mean that generating rtf is faster than pdf? is it beause migradoc has to turn migradoc objects into pdfsharp object and then draw, and rtf just renders?
Thomas Hoevel wrote:
Maybe run the code in a profiler and identify the routines in MigraDoc that consume most of the time.
From what I can tell on my end the only part that is holding back the program is the RenderDocument method, othern than that are you saying I should profile the migradoc code?.