Jessica wrote:
Since you don't give an answer to the performance problem, does this mean migradoc is abandoned and not updated anymore?
I had missed you earlier post and only replied to your second post. Sorry.
MigraDoc is not abandoned. Some operations require time. The amount of time depends on the computer that is used.
You say there is a performance problem.
MigraDoc works fine for our use cases.
1100 pages in 25 minutes, that is 44 pages per minute or about 1.5 seconds per page. Not good, but it works.
Table rendering is a bit slow for large tables. An encyclopaedia with 1100 pages should render much faster, assuming most of the text is outside of tables and only small tables are used.
It is possible to run the document generation in a profile to see which parts of the code consume most of the time. You have the code, so you can do it.
I don't have your code, so I cannot do it.
That's what I did to make MigraDoc much faster some time ago, using my test code and my test table.
I'm not the original author of this MigraDoc implementation.
For your use case, PDFsharp could be the better choice, assuming that performance is very important. Implementation takes a bit longer, but rendering will be much faster.