You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing a memory usage issue when creating very large Excel documents using fastexcel. While inserting cells into a worksheet with maximum dimensions (16,384 columns by 1,048,576 rows), I noticed that the memory consumption was extremely high.
Here are some specific observations:
Memory Usage: I measured memory consumption with VisualVM and observed usage of over 8 GB of RAM.
Memory Profiling: The profiling showed more than 180 million instances of org.dhatim.fastexcel.Cell and over 1 million instances of org.dhatim.fastexcel.Cell[].
I propose implementing a new version of the Worksheet class that writes cells directly to the document without keeping them in memory for potential future modifications. This sequential writing method is particularly useful for those, like me, who need to create large documents "cascadingly" without needing to know the content of previously written cells.
This solution would significantly reduce memory usage for large documents, improving the library’s efficiency in similar scenarios.
Thanks a lot 💯
The text was updated successfully, but these errors were encountered:
Problem
I am experiencing a memory usage issue when creating very large Excel documents using fastexcel. While inserting cells into a worksheet with maximum dimensions (
16,384
columns by1,048,576
rows), I noticed that the memory consumption was extremely high.Here are some specific observations:
Memory Usage: I measured memory consumption with VisualVM and observed usage of over 8 GB of RAM.
Memory Profiling: The profiling showed more than 180 million instances of
org.dhatim.fastexcel.Cell
and over 1 million instances oforg.dhatim.fastexcel.Cell[]
.Code Example to Reproduce the Issue
Proposed Solution
I propose implementing a new version of the Worksheet class that writes cells directly to the document without keeping them in memory for potential future modifications. This sequential writing method is particularly useful for those, like me, who need to create large documents "cascadingly" without needing to know the content of previously written cells.
This solution would significantly reduce memory usage for large documents, improving the library’s efficiency in similar scenarios.
Thanks a lot 💯
The text was updated successfully, but these errors were encountered: