Handling Large Excel Files using Aspose cells

Aspose.Cells Product Family
6

ok thanks for the update.
Meantime we are trying implement LightCellsAPI.

With the sample code/the explanation put in the documentation, we could only insert dummy data and unable to use the Data read using Read API.

We would like to know if there is a way where we can copy the data from the sheets as well write data to one of the sheets using LightCellsAPI. Any documentation with better examples can help us understand the implementation

7

@Mveerabaghu,

The examples provided in the Using LightCells API document are generic and for reference purposes, you may write your code accordingly. Moreover, even using LightCells API might not make big difference for your scenario/case. Anyways, you may try it until we implement caching cells data in the temporary file instead.

Could you please share a standalone console application (source code without compilation errors) with resource file(s) to demonstrate how you are implementing the LightCells API? Please zip the project prior attaching. We will check your sample soon.

8

@Mveerabaghu
Because you need to update the specific sheet and then resave the workbook to get the whole excel file with all worksheets(including those sheets without modification), we are afraid LightCells cannot help to achieve this goal. LightCells is mainly designed for streaming read from/write to excel file without keeping all cells data in memory. Because you need to re-save the workbook, all data of the workbook need to be kept in memory, so LightCells cannot decrease the memory cost for your scenario when keeping all data in memory.

If the large dataset has been split into many sheets in your template file and loading one sheet only every time does not require large amount of memory, LigthCells may be one possible solution:

  1. Load the template file with LoadFilter to load the sheet which you need to update only.
  2. Update the data in the loaded sheet
  3. Save the workbook with LightCells( Interface LightCellsDataProvider | Aspose.Cells for .NET API Reference). In the implementation of StartSheet, load the specific sheet only with LoadFilter from the template file, and then use the cells data in the newly loaded sheet to fill the objects to be saved(provided by StartRow and StartCell).
9

I am having an Excel of 1 GB , and using a dedicated Azure Function which has capacity to scale upto 14 GB memory and the function does the below operations

  1. Download the stream - takes approx 30 sec
  2. Initialize the workbook — bottleneck
  3. Update 1 worksheet
  4. Calculate workbook
  5. Get stream from workbook – bottleneck
  6. Upload to sharepoint.

the function goes unreachable starting point 3 and the max time out we can have is 10 minutes. As i understand available memory is not an issue in this case, still i m not able to accomplish on updating the workbook.
Could you share an approximate benchmark on file size Vs the CPU utilization and approximate time taken. this will help us to plan the infrastructure better, as at this point we dont not have any solution. is there a documentation around it?

Regarding the Issue ID(s): CELLSNET-54534, could we have some more details on what to expect in terms of

  1. maximum file size it would support
  2. exception handling around out of memory scenarios
  3. required infrastructure on this
  4. support for readonly workbooks or updates to selective sheets in an efficient way…
10

@Mveerabaghu
Thank you for your feedback. We will further investigate your issue. Once there is an update, we will notify you promptly.

11

hi team,
wanted to check if we have any updates on this issue as we are approaching end of year. Issue ID(s): CELLSNET-54534.
could you also share some details around this.

12

@Mveerabaghu,

We apologize, but the requested feature/issue has not been implemented/resolved yet. We will check if we can provide you with an estimated time of completion. We will get back to you soon.

13

@Mveerabaghu,

We plan to start this task in next month. We will try to implement the feature before the end of December 2024 (next month), provided there are no other higher priority or urgent tasks that may impede its progress.

14

ok thanks for the update! Keep us posted.

15

@Mveerabaghu,

Alright, we will provide you with new updates as soon as they become available.

16

hi team,
do we have any updates on this?

17

@Mveerabaghu

We apologize, but the feature (Ticket ID: “CELLSNET-54534”) has not been implemented yet. We are actively working on it and will see if we can provide you with the latest updates on it. We may reach out to you soon.

18

@Mveerabaghu

We apologize for not being able to complete this requirement according to the original timeline. Due to adjustment of the schedules and priorities of our tasks, development on this requirement has been interrupted. Based on our current progress, it may take another month or even longer before we can resume work on this task. Based on this timeline, we expect to try to support this feature by the end of the first quarter.

19

hi team,
wanted to check if we have any updates on this ticket?
Thanks

20

@Mveerabaghu
We deeply apologize, but this feature (Ticket ID: “CELLSNET-54534”) has not yet been implemented. We are still working hard to solve your issue. We will get back to you soon.

21

hi Team,
wanted to check if we have any updates on this ticket?
Thanks

22

@Mveerabaghu
We deeply apologize for any inconvenience caused to you. But this feature (Ticket ID: “CELLSNET-54534”) has not yet been implemented. This feature is quite complex, and we need more time to solve it. Once there is an update, we will notify you promptly. We will get back to you soon.

23

ok thanks for the update.
may i get a tentative date on this?

24

@Mveerabaghu
Thank you for your feedback. This task is quite complex. We have been working hard to support it. We need to further evaluate the follow-up work, and if possible, we will give you an approximate time. We will get back to you soon.

25

@Mveerabaghu
We are pleased to inform you that we have made significant progress in handling large files. We will support this feature by the end of June 2025. We will notify you immediately once there are any updates.