Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed too slow when writing mat73 #85

Open
zhengliuer opened this issue Nov 11, 2024 · 6 comments
Open

Speed too slow when writing mat73 #85

zhengliuer opened this issue Nov 11, 2024 · 6 comments
Assignees

Comments

@zhengliuer
Copy link

Dear all,

I successfully wrote my data to .mat v7.3, but I noticed the speed was extremely slow. To compare, the same data cost me less than 1sec to write a v5 .mat, but about 47sec for a v73.

Is this as expected? Has anyone faced the same problem with me? Any ideas to solve this?

I will keep trying to find out why and the solution of it.

Best,
Zheng

@zhengliuer zhengliuer changed the title Speed optimization when writing mat73 Speed too slow when writing mat73 Nov 11, 2024
@traversaro
Copy link
Collaborator

Indeed the time seems quite a lot, but if there is an issue, it may be more in matio https://github.com/tbeu/matio I guess, as matio-cpp only provides a C++ interface for the C functionalities provided in matio.

Anyhow, before opening an issue there, I think it make sense:

@zhengliuer
Copy link
Author

Thanks! I will discuss the issue there.

@zhengliuer
Copy link
Author

tbeu/matio#261 (comment)

I opened an issue in matio.

@traversaro
Copy link
Collaborator

I think that the mre should use matio, not matio-cpp, otherwise the mantainer does not know if the problem is in matio or matio-cpp. Furthermore, I would wait for having a working mre before opening an issue.

@S-Dafarra
Copy link
Member

Hi @zhengliuer, did you happen to find the source of your issue?

@zhengliuer zhengliuer reopened this Nov 26, 2024
@zhengliuer
Copy link
Author

zhengliuer commented Nov 26, 2024

Hi @zhengliuer, did you happen to find the source of your issue?

Sorry, no. I was occupied by some other things, so I closed the issue for now. Now I have some time for this. And luckily, according to the test result from tbeu/matio#261 (comment), the performance degradation is confirmed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants