GC.Collect() in Aspose.PDF

Aspose.PDF Product Family
1

Hi,

We are auditing our performance and we noticed that Aspose.PDF.PDF.Save(String) seems to be calling GC.Collect() when given a JPG or BMP file. Can you confirm this behavior? We are using version 4.1.1 of Aspose.PDF.dll.

Thanks,

Albert

2

Hello Albert,

Thanks for using our products.

Yes you are correct. Internally we are utilizing GC.Collect in our image rendering code. Are you facing some issue while working with Aspose.Pdf ? Please share some details.

We apologize for your inconvenience.

3

How would you suggest Aspose.Pdf be used in a server environment? The GC.Collect() impacts performance negatively.

Thanks,

Albert

4

Hello Albert,

Can you please share some code snippet / sample project so that first we can test the scenario at our end. We are sorry for your inconvenience.

5

I don’t believe code is needed here. On a long running server side code that uses the functions in question will induce GC collects that not only GC on the Aspose code, but the rest of the server code too. This have negative impact on performance. Is there a reason why it could not be left for the GC to naturally collect and you have to force a GC?

6

Hi Albert,


We are actually using GC.Collect in order to avoid some issues in GDI+
for image processing (tested on WinXPSP2 .NET 2.0). We don’t test this
issue on a server system, so my be our trick make not sense in this
case. Anyway, we are going to review and re-test the GC.Collect usage in
our code.

May you provide a little bit info about your working environment - OS,
NET version?
7

To answer for AWong,

The production environment is a 64-bit Windows Server 2008 (SP1) with 32GB of RAM, NET version 3.5 and dual quad-core processors. The Gen 2 collections happen roughly every 100 seconds under normal working conditions. That should be plenty soon enough to clean up memory. Furthermore, if there is a high amount of volatility in the Gen 2 Heap, then an additional collection is already performed by the garbage collector.

8

The issues you have found earlier (filed as 21519) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.