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

madmax don't wait for copy before continuing? #92

Open
markkundinger opened this issue Jul 9, 2021 · 11 comments
Open

madmax don't wait for copy before continuing? #92

markkundinger opened this issue Jul 9, 2021 · 11 comments

Comments

@markkundinger
Copy link

madmax has the option -w, --waitforcopy

I don't see a way to pass that option in plotng?

Right now in the madmax windows port it looks like it's waiting for the copy to finish before starting again. and that is effectively a penalty of 10 or 20 minutes in my case when copying across network.

@maded2
Copy link
Owner

maded2 commented Jul 10, 2021

unfortunately, that option is only for when using madmax in standalone mode to generate multiple plots

@sochkumar
Copy link

sochkumar commented Jul 11, 2021

so is there any way to implement this copying thing ? because right now its not starting new plot until the existing plot is copied. It should behave as default madmax which keeps plotting and copying simultaneously

@maded2
Copy link
Owner

maded2 commented Jul 12, 2021

I personally uses a local disk for staging the finished plots and then a script rsync it to the farmer. In your case you can do the same to your NAS. This means that the madmax plotter will not need to do wait.

@markkundinger
Copy link
Author

That's unfortunate. In my case it's a 70 minute plot and a 15 minute copy. That's a signicant slowdown on a percentage basis and I'd rather just run madmax naked.

In theory maybe I could set my destination drive to the same as my temp for instant copy (?) But I'm not smart enough to script a copy to my nas.

Plotng works by triggering one madmax plot at a time right? That could be tricky to refactor...

What is there was an option to tweak when plotng thinks max is "done"? Instead of waiting till the copy is finished, wait until all passes are complete, let max begin the copy, and then launch a new instance. So they'd technically be running in parallel but only until the copy is done.
?

@graid2030
Copy link

graid2030 commented Jul 13, 2021

In this pull request, I added an option that allows you to start the next plot without waiting for the previous one.

@sochkumar
Copy link

In this pull request, I added an option that allows you to start the next plot without waiting for the previous one.

have you implemented tmp2 directory thing for madmax like in actual plotng ? can't see that in your config

@maded2
Copy link
Owner

maded2 commented Jul 14, 2021

In this pull request, I added an option that allows you to start the next plot without waiting for the previous one.

have you implemented tmp2 directory thing for madmax like in actual plotng ? can't see that in your config

tmp2 support is already in the PlotNG. But currently it only support single tmp2 directory. I am assuming not many people have the ram to have 2 of them.

@sochkumar
Copy link

sochkumar commented Jul 14, 2021

yes but AsyncCopy which the other user (graid2030) did in his PR is not there in main branch. Is it possible to merge into main or have this option incorporated ? background copying while starting new plot is very important or else its really waste of time to wait for the copy to finish and start new plot after that

@sochkumar
Copy link

Anyone on this ?

@maded2
Copy link
Owner

maded2 commented Jul 15, 2021

will try to reviews the changes this weekend

@sochkumar
Copy link

Thanks

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

4 participants