Aspose.Slides memory usage

We’re upgrading Aspose.Slides for java from 14.10.0 to 15.5.1. We have a bunch of load tests on our end, which started to failing after this upgrade. Moreover we started experiencing OutOfMemoryException’s on heap during these load tests.
So we went and took bunch of pptx files and did a profiling for these 2 versions of libraries.
Following code is the only code which was profiled:

License license = new License();
license.setLicense(“Aspose.Total.Java.lic”);
Presentation presentation = new Presentation("INPUT_FILE);

Average results is that memory consumption by library has increased and processing time as well increased. For some files we had really bad results(one of them attached). For the attached file(23MB in size) processing time has increased by 3 times(when XMS=XMX =2GB). That is probably due to significantly higher memory consumption: we can observe GC works out several times during DOM is built by library. If JVM is given more memory - 6GB - processing time reduces, but library eats up to 4GB of memory.
So the purpose of this message is following:
Possibly you can get a clear answer from your development team - why this particular file requires so much memory/ find and fix memory inefficient code.
We’re afraid that we might not be able to handle the expected load on our servers even with increased memory, if that remains the tendency in new versions of libraries. Right now this looks quite scary, hopefully it will not get any worse.

In the attachment you will find a test file and a Heap memory telemetry gathered from the code snippet of code above run with 2 versions of libraries.

Hi Andrey,

I have observed the details shared by you and like to share that we are continually working over improving the API performance on our end on every product release. I have created an observation ticket with ID SLIDESJAVA-34946 in our issue tracking system to observe the presentation file shared by you and see if the highlighted memory and performance related issues for the shared presentation is valid. Our product team will schedule and investigate the issue and we will share the feedback with you once it will be shared by our product team.

We are sorry for your inconvenience,