Multi-Core / Utilization Dedicated WIN Server

    Joined
    Jun 25, 2013
    Messages
    4
    Reaction score
    0
    SPECS:

    WIN 2008 R2 Standard SERVER SP1, 64 BIT

    Intel Xeon CPU L5420 2.50GHz 8 CORES.

    8 GB RAM

    1GB Connection

    PROBLEM:

    Ultilization of all avaliable cores is not apparent in running a server. Even running the game on a "true dedicated" system, Starmade experiances bottlenecking issues preventing it to all avaliable cores in mulitcore computers.

    This issue does not make the game unplayable but does drasticly limit the the amount of players a server can handle.

    PICTURE:

    https://dl.dropboxusercontent.com/u/5493561/TS3%20ICONS/Peek.png

    https://dl.dropboxusercontent.com/u/5493561/TS3%20ICONS/Peek2.png

    These pictures are of my remote server. Notice CPU Usage of 4th core capping higher with all other cores quite low on usage. That was taken with 35 players on and 2 Hours after innitial launch. .

    I hope the info posted here can be resolved in a later build of the game and or launcher options.
     
    Joined
    Jul 9, 2013
    Messages
    1
    Reaction score
    0
    • Legacy Citizen 2
    • Legacy Citizen
    This is one of the more urgent issues. I have a salvaging ship that\'s supposed to mine over 2000 blocks a second - with all those hit detections running on a single core. I would not only urge implementing multithreaded code, but even GPU acceleration to handle blocks.

    I have one of the worst architectural match-ups for running this game - namely AMD FX box, which is prone to higher temperatures and has inefficient single-thread performance. So mining a planet at a rate of over 2000 blocks a second on a single core is ridiculously demanding. The issue is not as much the 7 cores being unneccesarily idle at 37 Celsius, but, and this is the scary part, a single core running on full load in turbo mode for as long as I keep my left mouse-button pressed down - I recorded a peak temperature reading of 224 Celsius on this core. This is probably a fluke in the temperature reading algorythm, but seriously...