Here Time is the time that Clingo took to solve the problem, as given in stdout by Clingo itself. Actually, if you notice the 41' approximates better to pre-processing+Time.
Solve time and CPU Time are also in the Clingo output, the solve time is Time excluding Clingo's command preprocessing (not the one we do on Pre-processing Time) and grounding, so the amount of time the clingo command took in solving exclusively.
As for CPU Time, I understand it is what you say, the total CPU time over threads for solving.
The Max Memory was bugged, I must have introduced a bug in one of the latest updates, but I found it and fixed it earlier today. We will have to run it again to know how much memory it used :-). The memory metric of the output is in MBs.
Hello @ssardina ,
Here
Time
is the time that Clingo took to solve the problem, as given in stdout by Clingo itself. Actually, if you notice the 41' approximates better to pre-processing+Time. Solve time and CPU Time are also in the Clingo output, the solve time isTime
excluding Clingo's command preprocessing (not the one we do onPre-processing Time
) and grounding, so the amount of time the clingo command took in solving exclusively. As for CPU Time, I understand it is what you say, the total CPU time over threads for solving.The
Max Memory
was bugged, I must have introduced a bug in one of the latest updates, but I found it and fixed it earlier today. We will have to run it again to know how much memory it used :-). The memory metric of the output is in MBs.Originally posted by @idrave in https://github.com/idrave/FOND-ASP/discussions/27#discussioncomment-1291229