Slow JpegDevice.Process in Aspose.PDF.Drawing 2 minutes to convert 1 page

I experience slow PDF to Jpeg convertion for 3% of the PDF file after I recently switched from Aspose.PDF to Aspose.PDF.Drawing Version=“24.1.0”
They took 2.5 minutes to process, comparing to <25s previously

The code is JpegDevice.Process(page, imageStream);
The PDF is only 350 KB, 1 page.
There are plenty of memory and CPU capacity, 300MB memory is used.

I can’t share the PDF here for privacy, but it should be easy to reproduce

@jiangaayjake

Are you facing this issue with all type of PDF documents that you have? Also, can you please share the OS details where you are using the API?

Some PDFs generated from a number of templates are slower than others.
What are the types of PDF?

11th Gen Intel(R) Core™ i7-1185G7 @ 3.00GHz 3.00 GHz
32.0 GB (31.7 GB usable)

Windows 10 Enterprise
version: 22H2
os build: 19045.3803
experience: Windows Feature Experience Pack 1000.19053.1000.0

docker linux: dotnet/aspnet:6.0 AS base

They can be scanned, AcroForms, etc. On the other hand, every PDF document has different type of structure and complexity. Therefore, we request if you can please share a sample PDF with us as well with the docker file that you are using. We will further proceed to assist you accordingly.

Hi, are you able to resolve the issue? I am having the same issue on Windows machine when I switched from aspse.pdf to aspose.Pdf.drawing it is extremely slow

@Laksh

Aspose.Pdf.Drawing is generally released to be used under non-Windows environments. You can keep using Aspose.PDF for .NET on Windows unless you are forced to use Aspose.Pdf.Drawing due to your personal perferences.

Can you please share some sample file and the code snippet with us? Also, please share the time API is taking while performing same execution in your environment. We will test the scenario in our environment and address it accordingly.

Also, we believe that you have opened another thread related to this issue which is being responded as well. We request that you can please follow up there and share further information there as well.