We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Dramatic performance issues with latest Aspose.Total .NET

Hi,
We’ve just downloaded the latest version of Aspose.Total and noticed that the performance of converting slides and PDF pages to thumbnails has dropped dramatically.
Now our conversion tools run 10-15 times slower as GetThumbnail takes about a minute for each slide,

while before it was only a few seconds.

Here is the code we use:

var license = new Aspose.Slides.License();
license.SetLicense(“Aspose.Total.lic”);

var pres = new Presentation(stream);

foreach (ISlide slide in pres.Slides)
{
using (var imgStream = new MemoryStream())
{
var bmp = slide.GetThumbnail(1f, 1f);
bmp.Save(imgStream, System.Drawing.Imaging.ImageFormat.Jpeg);
imgStream.Position = 0;

// save
resolver(imgStream, “image/jpeg”, pagesCreated, pres.Slides.Count);
}
pagesCreated++;
}

Hi Denis,

Thank you for sharing the template file.

I have checked your issue with the latest version of Aspose.Slides for .NET v14.2.0 and it only takes 1 min and 22 seconds to convert all of the 49 slides to image. If your version is some older version, I would suggest you to try the latest version and share your results. In case you still face any issue, please share your environment details i.e. OS, .NET Framework etc. with us. We will further check the issue and get back to you.

Thanks & Regards,

Hi Ahmad,

We just installed the latest Aspose.Slides for .NET v14.2.0
on the Windows Server 2012.

The tools are compiled with .NET 4.5

The document attached is converted in 09 mins 57 secs.

If we revert the changes and use the previous version of Aspose.Slides, the document is converted in less than a minute.

Please test your binaries on the Server SKUs with .NET 4.5

thanks,
Denis

Hi Owais,


We have also tested Aspose.Slides for .NET v14.2.0 on Windows 8 with .NET 4.5

It’s the same problem with performance. So the Server SKU is not a problem.

Have you tested the binaries with .NET 4.5 and .NET 4.5.1?

thanks,
Denis

Hi Denis,

Thank you for the details.
We are checking the issue with .NET 4.5 and will get back to you shortly.

Thanks & Regards,

Hi Denis,

I have checked your reported issue on my Windows 7 machine with .NET Framework 4.5 and it took around 4 minutes and 21 seconds to convert the file. I have registered an issue with id: SLIDESNET-35340 in our issue tracking system to check this performance degradation with .NET Framework 4.5.

Also, I will further check on Windows Server 2012 to check the performance and will share the details with you.

Thanks & Regards,

Hi Denis,

Thank you for being patient.

Please download and try the latest version of Aspose.Slides for .NET version 14.4.0. I checked your template file on Windows Server 2012 and .NET Framework 4.5 and it took only 11 seconds to convert the file. Please try the latest version at your end and share the results with us.

Thanks & Regards,

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

<![endif]–>

Hello,


This issue still exists even in 14.7.0

I’ve installed new bits today and it takes more than 3 minutes to convert the slides, while the older version we used takes about 20 secs.

Our environment is Windows Server 2012 with .NET 4.5

thanks,
Denis

Hi Dennis,

I like to share that the issue is still unresolved. I appreciate your test with latest version Aspose.Slides for .NET 14.7.0 and have updated the issue in issue tracking system with your comments. We will share the feedback with you as soon as the issue will be resolved.

We are sorry for your inconvenience,