The EO .NET PDF converts 1 page PDF with very little content for more than 2 hours.
96041_DRTEST_3.zip linked here includes 96041_DRTEST_3.htm and 96041_DRTEST_3.htm.pdf.
No external CSS, no JavaScript.
Any EO version we tried is affected, including the most recent one. The online live demo is also having a problem converting this HTML. In fact, www.essentialobjects.com becomes unresponsive when a few such requests are submitted.
Not only EO takes a very long time to convert this HTML, but it also overloads CPUs while doing so.
This slows down response time for other requests or often leads to errors. It creates a very critical situation when a few of such requests are handled by a single server simultaneously, rendering the server unusable.
I hope a permanent solution is possible or there is at least a workaround.
Please, advise!

Standing alone Google Chrome however deals with it in a sub-second time and produces PDF with no problem.

The conversion methods of the EO.Pdf.HtmlToPdf class used:
public static HtmlToPdfResult ConvertHtml(string html, PdfDocument doc, HtmlToPdfOptions options);
public static HtmlToPdfResult ConvertUrl(string url, PdfDocument doc, HtmlToPdfOptions options); (with a local HTML file full path)

I hope this post will benefit the EO community.
We also found HTML content (just 78KB) that not only took 3+h while being converted to PDF but resulted in an OutOfMemory exception. Not 100% sure if it is the same issue as in the original post. In the first 10 minutes, memory consumption jumps to >90% on a 32GB server. While typical requests even in huge numbers barely move a needle on the memory consumption gauge.