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

big delay between solution was shown and solving end time. #720

Open
i-kudryavtsev opened this issue Aug 2, 2023 · 2 comments
Open

big delay between solution was shown and solving end time. #720

i-kudryavtsev opened this issue Aug 2, 2023 · 2 comments

Comments

@i-kudryavtsev
Copy link

Hello,

I have the following issue: I'm solving a relatively huge problem using Gecode. I can see that gecode solved (solution displayed) it, but something is still going on. This delay could be very significant, more than the solution time. For example, I can see the solution on my machine when the timer is on ~2:30, but it still needs to be finished at ~6:00.

My wild guess is that it's related to some memory cleaning. Could it be cut if only one solution is required?

Thanks in advance!
Ilya

@Dekker1
Copy link
Member

Dekker1 commented Aug 24, 2023

Hi Ilya,

The difference between the time would normally be explained by the output processing. MiniZinc takes the output from the solver and translates it back in terms of the model, evaluating the output model created during flattening. Usually this does not take much time, especially for solvers like Gecode, where the decisions representation is generally the same as in the MiniZinc model. For MIP or SAT solvers, it is not uncommon that this might take longer.

Since the output model can contain many type of functions, there is no limit on the amount of time. If you want to share the model where the time difference is so surprising, then we might be able to help explain it in the specific case.

@Dekker1 Dekker1 closed this as completed Aug 29, 2023
@guidotack
Copy link
Member

This is more likely to be the final cleanup of the garbage collector, which can take several seconds for large models. I'm working on a fix for this.

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

No branches or pull requests

3 participants