Aspose.Cells taking huge time to convert Excel to Tiff

Aspose.Cells Product Family
1

Hi Team,

I am using Aspose Framework (Aspose.cells dll version 8.5.1).
While trying to convert large excel file(no. of sheets-11, no. of rows-23228) to tiff image of file size 20 MB. It is taking huge time to covert into tiff around 4 hours with compression CompressionCCITT4. And without using compression it is throwing an exception. The generated Tiff file size is of 512 MB.
So I wanted to know:

  1. What is the maximum size of the excel file that Aspose.Cells is able to convert.
  2. What is the maximum limit on number of pages.
    3.What we can do to reduce the time for conversion.

Please provide solution to this problem.

2

@Sharvan,

There is no restriction or limits put forth by Aspose.Cells for rendering, it works the same way as MS Excel for creating or rendering Excel spreadsheets.

Regarding your issue “Aspose.Cells taking huge time to convert Excel to Tiff”, since you are using some older version of the product, so we cannot evaluate your issue using your older version on our end. Neither we can include any fixes to older version (if it has any issues or bug). We can only recommend you to kindly try using our latest version/fix, e.g Aspose.Cells for .NET v20.9.x. If you still find the issue with v20.9.x, kindly zip your template Excel file and paste your sample code (runnable) to show the issue, we will check it soon.

3

Hi Amjad,

Can you please let us know until which version it is supported by Aspose team.

Thanks.

4

Hi Amjad,

Can you please until which version it is supported by Aspose team.

Thanks.

5

@Sharvan,

Please note, we evaluate issues using latest APIs set only. Similarly we fix issues (if found) into newer versions only. Suppose there was some performance issue or other issue with some older version, we cannot fix the bug in older version, the fixes are based on latest APIs set.

We have improved the performance of Excel to TIFF rendering over the years. So it is better to try the newer version(s) and such issues might be fixed already in the recent versions. Also if latest version still shows your issue, we can evaluate it (using your provided file(s)) and try to give you the fix soon.