メインコンテンツへスキップ

Wall clock solve time spikes compared to reported optimizer time

回答済み

コメント

4件のコメント

  • 正式なコメント
    Simranjit Kaur
    • Gurobi Staff
    This post is more than two years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum, or try Gurobot, our chatbot interface offering instant, expert-level support.
  • Jaromił Najman
    • 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
    • Gurobi-versary
    • 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

    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

投稿コメントは受け付けていません。