Skip to main content

Wall clock solve time spikes compared to reported optimizer time

Answered

Comments

3 comments

  • Jaromił Najman
    Gurobi Staff Gurobi Staff

    Hi Brian,

    Is it correct that the difference you see is within ~0.02 seconds? It might be possible that some Thread is blocking the access to get the CPU time. Are you running something in parallel or in the background?

    Best regards, 
    Jaromił

    0
  • Brian Acosta
    First Comment
    First Question

    That is correct. I investigated a little more and found that when I remove read permissions for the file "/proc/cpuinfo", the discrepancy goes away. This is consistent with the hypothesis that reading that file is the problem. I also confirmed that I don't see this discrepancy on macos, potentially due to a different implementation for retrieving the cpu info.

    0
  • Jaromił Najman
    Gurobi Staff Gurobi Staff

    I investigated a little more and found that when I remove read permissions for the file "/proc/cpuinfo", the discrepancy goes away. 

    Good that you were able to figure this out. I think this is a good indicator that there were some conflicts when trying to access the file.

    Best regards, 
    Jaromił

    0

Please sign in to leave a comment.