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

Log solving profiles #1124

Closed
jcoupey opened this issue Jun 10, 2024 · 0 comments · Fixed by #1154
Closed

Log solving profiles #1124

jcoupey opened this issue Jun 10, 2024 · 0 comments · Fixed by #1154

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Jun 10, 2024

The only debug info we currently have related to the local search process is a count of the number of time each operator is applied. To further analyze the current solving pattern, and the impact of further changes (e.g. #874), it would be useful to log the evolution of each of the parallelized search process:

  • current solution indicators;
  • time;
  • triggering event, such as operator application, job addition, solution R&R etc.

We could then have a few scripts to analyze and plot the data in https://github.com/VROOM-Project/vroom-scripts/.

@jcoupey jcoupey added this to the v1.15.0 milestone Jun 10, 2024
@jcoupey jcoupey mentioned this issue Jun 11, 2024
5 tasks
@jcoupey jcoupey mentioned this issue Sep 13, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant