Details

    • Type: Sub-task
    • Status: Done
    • Priority: High
    • Resolution: Done
    • Labels:
      None

      Description

      Problem
      Limit / reduce startup Navmesh gen CPU usage. Currently navmesh gen uses all cores at 100%.

      This will likely cause owners who host multiple servers or shared hosting server providers quite a lot of issues. Many shared providers shutdown / auto restart servers with high CPU usage meaning they may not startup.

      Update (as this issue has been linked alot)

      • Added nav_wait cvar (default true)
        If true we'll wait for the navmesh to generate before completely starting the server. This might cause your server to hitch and lag as it generates in the background.
      • Added nav_disable cvar (default false)
        If set to true the navmesh won't generate.. which means Ai that uses the navmesh won't be able to move

        Attachments

          Activity

          Hide
          bawNg bawNg added a comment -

          If the navmesh generation can't be optimized, it'll probably need to be cached to disk too, since it currently increases boot times a massive amount even with unlimited CPU usage. It took over 5 minutes to generate for an empty 4500 size map on a 4.2gHz CPU.

          Show
          bawNg bawNg added a comment - If the navmesh generation can't be optimized, it'll probably need to be cached to disk too, since it currently increases boot times a massive amount even with unlimited CPU usage. It took over 5 minutes to generate for an empty 4500 size map on a 4.2gHz CPU.
          Hide
          tyran Alasdair added a comment -

          This is actually causing servers to become unusable during boot, at the moment it is not economical to host more than 2 servers on less than 8 dedicated cores at 4.0Ghz+. Multi-threading Xeon E3/E5 also has the same problem.

          Show
          tyran Alasdair added a comment - This is actually causing servers to become unusable during boot, at the moment it is not economical to host more than 2 servers on less than 8 dedicated cores at 4.0Ghz+. Multi-threading Xeon E3/E5 also has the same problem.

            People

            • Assignee:
              garry newman Garry Newman
              Reporter:
              Alistair Alistair McFarlane
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: