Open DmitriiGaidukov opened 3 years ago
I don't have a solution at the code level, but one alternative is to re-think the infrastructure design of the pdf generation, which we can think of it like a reporting service.
If working on cloud, we can also opt to dynamically spool up a temporary application to execute the job, and then self terminate when completed. With on-premise infrastructure, it may be possible to home brew something similar.
In my ASP.NET Core app, I run into a problem with the Synchronized converter that multiple web requests are queued on a single thread instead of running in parallel and/or utilizing all cores. I take it it is the expected behavior:
Is there a way to work around this limitation? For ASP.NET Core apps it's a really big issue as they are inherently multithreaded.