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

Free Support Forum - aspose.com

Performance issue when merging Slides of a PPT to another PPT

Aspose.Slides Product Family
#1

Hi,

We have arequirement where we have to stitch multiple PPTs into a single PPT. Around 50 PPTs have to be merged as a single PPT. we have used CloneSlide method, where we iterate to all the slides in 50 PPTs and merge them. But it takes around 3 mins to finish that process where as to merge 50 PDFs it takes only few seconds.

Functions that are used in the loop are :

1) Creating instance of Parent presentation to which the slides of other PPT have to be appended. In this case from the 50 individual PPTs, the first one is considered as the parent. and a loop rund for 49 times to merge the slides of other PPT with the parent PPT.

2) CloneSlide method to attach the slides of 49 ppts to the parent ppt.

3) WriteFile method to save the PPT at the end of every iteration.

Is there a method to stitch the PPTs without having performance degradation? We are using Apose.Slides for .Net version 8.3.0.0

Thanks,

AnuradhaV

#2

Looks like its taking a lot of time to create Presentation object as the parent slide grows in size.

#3

Hi AnuradhaV,

Thanks for inquiring Aspose.Slides.

I have observed the requirements shared by you and like to share that whenever you load the presentation using Aspose.Slides, it gets loaded in memory inside Document Object Model (DOM) of Aspose.Slides. The loading time varies from number of slides and content inside the slide. Secondly, one cannot compare the loading and merging of PDF with that of loading and merging of presentations. These two formats are totally different internally and cannot be compared.

I also suggest you to please try using Aspose.Slides for .NET 14.8.0 on your end as well, which is latest version to date. If you feel any performance issue then please share the sample presentations, sample application, machine specifications and statistics achieved on your end with us. We will investigate that further on our end to see if the statistics that you are achieving on your end is actually a performance related issue or not.

Many Thanks,

#4

Thank you for your response.

The parent PPT size will keep increasing in every iteration and it is observed that the time taken to instantiate the Presentation object with the Parent PPT in every iteration increases which injects a time delay.

If we are going to use the higher version of Aspose.Slides, then will we be facing any issues with the other Aspose.Slides functions that are being used? Can the higher version DLL be used the same license that we already procured for Aspose.Slides 8.3.0.0 version?

Thanks,

AnuradhaV

#5

Hi AnuradhaV,

Thanks for your feedback.

I have observed your following comments regarding the PPT size:

The parent PPT size will keep increasing in every iteration and it is observed that the time taken to instantiate the Presentation object with the Parent PPT in every iteration increases which injects a time delay.
As requested earlier, please share the sample application, generated presentations, machine specifications and statistics achieved on your end. But before sharing with us, please verify using latest Aspose.Slides for .NET 14.8.0 on your end as support is available if the issue is reproduced in latest version. Also the product series that you are using is no longer supported and is discontinued.

As far as your license subscription is concerned, your license will work with latest version if its expiry date is greater then release date of Aspose.Slides for .NET 14.8.0.

Please share, if I may help you further in this regard.

Many Thanks,