|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #55427] save -v7 exits with "error compressing data element" |
Date: | Sun, 4 Jul 2021 06:16:18 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 |
Follow-up Comment #17, bug #55427 (project octave): It occurred to me that I could also try to load the individual .mat files directly in Matlab; I'll do that tonight. My aim was primarily to check if Octave correctly saves the various compressed data. Your explanation (thanks!) almost makes for another feature request: Octave showing its overhead for storing data structures :-) Could be enlightening if not confronting info. I already figured years ago that the "gis" struct in my example is probably quite memory-inefficient; each field contains structs containing o.a., struct arrays of grids each with fairly different dimensions. There must be a lot of "air" in the data structure in RAM. But I didn't expect a factor of 4 even in Matlab ... (OTOH that struct is very efficient for how it is used, but that's quite another story) _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55427> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |