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

Meshing taking over 14 hours #195

Closed
Sarngond opened this issue Aug 17, 2018 · 13 comments
Closed

Meshing taking over 14 hours #195

Sarngond opened this issue Aug 17, 2018 · 13 comments
Labels
stale for issues that becomes stale (no solution)

Comments

@Sarngond
Copy link

Sarngond commented Aug 17, 2018

I don't know if this is my fault or Meshroom's but I put 68 images in and once it got to meshing it has already taken 14 hours and is still going. I don't know if this is normal or what, i just want to know if you guys think my model will be done soon. It has currently been on Comute boykov_kolmogorov_max_flow since 23:10:14.

@Sarngond
Copy link
Author

should I just stop the process cuz it's still going.

@Sarngond
Copy link
Author

I went ahead and stopped it.

@Sarngond
Copy link
Author

does anyone know why it was taking so long?

@simogasp
Copy link
Member

can you share your images in private (alicevision-team@googlegroups.com)?
@fabiencastan @yann-lty @gregoire-dl will try to launch it and debug it as soon as they are back from SIGGRAPH.

@fabiencastan
Copy link
Member

How much RAM do you have on your machine?
You should reduce the value of maxPoints to avoid using too much RAM & SWAP.

@Sarngond
Copy link
Author

what are maxPoints? Are they some value in Meshroom? I have 12GB of RAM

@fabiencastan
Copy link
Member

fabiencastan commented Aug 20, 2018

It's a parameter of the Meshing node (here in the code).
If you have 12GB, you definitely need to reduce this value.
We should add something to adapt to your machine resources, but in our use case we compute on renderfarm and use some constraints to get machines with >= 32GB.
I don't know the exact mapping from this value to the RAM needed. So you should try 1000000 first, and then 2000000 which should be fine too.

@shootie22
Copy link

can you change the value while it's running and it will continue the process, but start the meshing with the new value? or are you supposed to stop everything, modify the value and then start it again?

@fabiencastan
Copy link
Member

@Sarngond : Does this allow you to compute the Meshing node?

@urgaylol : If you change the parameters of a node while the node is being computed, the parameter changes will have no impact on the current computation.

@cyberprodigy
Copy link

In latest MeshRoom, double clicking Meshing node and lowering values helped me to get further
image

I went pretty low. I am not an expert but I think the lower you go, the less ram it will use, so play around with it.

@brothermechanic
Copy link

brothermechanic commented Apr 17, 2019

In latest MeshRoom, double clicking Meshing node and lowering values helped me to get further
image

I went pretty low. I am not an expert but I think the lower you go, the less ram it will use, so play around with it.
@cyberprodigy
Same issue - looong time meshing
Thank you for workaround!

@stale
Copy link

stale bot commented Aug 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale for issues that becomes stale (no solution) label Aug 25, 2019
@stale
Copy link

stale bot commented Dec 10, 2019

This issue is closed due to inactivity. Feel free to re-open if new information is available.

@stale stale bot closed this as completed Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale for issues that becomes stale (no solution)
Projects
None yet
Development

No branches or pull requests

6 participants