Why is save/load write/read soooo slooooow?

30 次查看（过去 30 天）
Ron Abileah
Ron Abileah 2013-9-3
评论： xingxingcui 2021-8-24
I used a save myworkspace at a point when I want to interrupt a long process, and sometime later I do a load myworkspace to restore the interrupt point and continue.
The typical mat file produced by this procedure is 18 GB. The save takes 1200 seconds, the load takes 350 seconds. The times are the same using a single HDD or a SSD cluster in Raid0 configuration.
On the same computer I can use the OS to copy a 18 GB file in 65 seconds on HDD, 30 seconds on SSD.
So it appears that Matlab save/load have some serious bottlenecks. Is there anything I can do differently? Is this something I should raise to Mathworks Support?
  9 个评论
显示 7更早的评论
Cedric
Cedric 2013-9-12
I think that even this partial answer will be useful information for the next persons who are facing this issue and who find your thread!

请先登录，再进行评论。

请先登录，再回答此问题。

采纳的回答

per isakson
per isakson 2013-9-8
Doc says:
save(filename, ..., version) saves to MAT-files in the specified version:
'-v4', '-v6', '-v7',or '-v7.3'.
and
'-v7.3'7.3 (R2006b) or laterVersion 7.0 features plus support for data
items greater than or equal to 2 GB on 64-bit systems.
18GB requires v7.3, which is slow. v6 is significantly faster. v6 might be an alternative if you can split the data into <2GB chunks.

更多回答（1 个）

Jan
Jan 2013-9-9
编辑：Jan 2013-9-9

类别

在 Help Center 和 File Exchange 中查找有关 HDF5 的更多信息

标签

产品

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by