Optimise memory on exports
Issue #116
resolved
A 6500 study CT xlsx export was killed because the computer it was running on ran out of memory.
xlsxwriter has a memory optimisation mode that might solve this - there are restrictions though on how data is written, as each row is flushed to disk in turn, meaning you can't go back.
Need to establish whether this has any consequences.
Comments (5)
-
reporter
-
reporter
MIssed a colon in the warning added to docs ref
#116→ <<cset f909548f6ad6>>
-
reporter
Optimisation still needs to be done, and the memory optimisation mode might be part of this. But I haven't seen this issue since, and I haven't changed how much memory is available, so I will take it out of the docs.
-
reporter
Removed warning about ref
#116→ <<cset 425eafa0e1cb>>
-
reporter
- changed status to resolved
Closing as does not appear to be an issue in 2022
- Log in to comment
Added note regarding memory issues with large exports to docs. Refs
#116.→ <<cset 3f150f7b3191>>