-
Notifications
You must be signed in to change notification settings - Fork 6
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
Too slow in recent Mathematica 11 #1
Comments
Bummer! Sadly this was written in a much older version of Mathematica (7?) and hasn't been updated... If you can figure out an improvement please send a PR! |
Well, it's probably not the problem of Mathematica version. It's a
problem that Export works very slowly on some large files,
while NotebookSave works fast. On the other hand, we do not want to
use NotebookSave. So, I am not sure how to improve.
…On 04/01/17 16:08, Josh Burkart wrote:
Bummer! Sadly this was written in a much older version of Mathematica
(7?) and hasn't been updated... If you can figure out an improvement
please send a PR!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADTdBtKsjcyQBYClSLn0fLtClei0GEuSks5rO8QPgaJpZM4LaxQO>.
|
Ah, actually, I remember noticing the speed difference too. Yep I'm not sure how to work around this either, other than by using smaller notebooks... Sorry! |
I have experienced this too. It is prominent in notebooks with lots of large images. This makes the FrontEnd hang for quite some time after evaluations when the timeout for the auto-save has been reached again. Is there really no way to fix this? Why should we not use NotebookSave? |
I applied the following changes:
I had some trouble with RenameFile failing and NotebookSave adding .nb, but this works and seems much faster. This seems to do what I want. Someone should report to WRI the NotebookSave <-> Export performance discrepancy. |
@Masterxilo Thanks for looking into this! My recollection was that using I believe the issue is that If your solution works with no deleterious side effects then please consider sending a PR! |
Oh sorry, I see now that you got around this. Well in that case looks good to me! The slowness of using |
Sure! I would prefer to get With my fix I get |
Ahh, yeah. Also, does this mean every time there's a backup, the notebook also gets saved? To its normal save path? |
Yes. This might be problematic if the notebook becomes corrupted (making the original and the backup unusable on the next backup). |
This seems to work MUCH slower than the ordinary "Save" button in Mathematica 11. I do not know, why. Probably, some other saving command should be used in the script.
Thanks,
Sergey
The text was updated successfully, but these errors were encountered: