DreadPirate

  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

7 Neutral

About DreadPirate

  • Rank
    Junior Member
...

Badges

Recent Profile Visitors

433 profile views
  1. Ok, so more info to report... I hope this helps. Tonight we had a player with a ping of over 700. He was on a satellite connection and didn't have much control over it. He helped me try a few things... we profiled the server a few times as he was playing. I restarted the server, dropped it to 20 ticks and profiled it again...anytime he was playing the host was a Bad Host, and there were massive issues with rubberbanding and overall desync. After a bit, we had him stop moving... once he did that we the host upgraded to OK, and the rest of us experienced no lag issues at all... until he started moving again. Attached is a zip archive with some profiles, the 700 ping bad is when he was actively playing, the 700 ping ok was when he was stopped. I hope this help, I'll keep trying to give you guys profiler logs when I see something odd. DST_Profiler_Logs_700_Ping.zip
  2. Team, Here is another set of logs from today. Sorry for the delay in getting back to you, it's been a crazy week at work. In the zip file there are multiple profiles. The profiles are numbered in order they were taken 01 was before 02, etc... The profiles also have a status of good, ok or bad depending on what the server was reporting as in game. I hope some of this helps, let me know if you have any questions. Thanks again for taking a look at these. DST_Profiler_Logs.zip
  3. Kaj, No apologies needed! This is early access... it's for squashing bugs... sometimes for squashing bugs in tools needed to squash more bugs I'm happy to run the profiler again whenever you are ready.
  4. Hello there everyone! I gathered some profiles from our public test server and zipped them up for you. In the archive, please find the following files: profile_1.json profile_2_bad.json profile_3_bad.json profile_4_bad.json profile_5_ok.json profile_6_ok.json I don't remember if profile 1 is Good Host or OK Host. Profiles 2 - 4 are when it was listed as Bad Host. Profiles 5 & 6 are when it went from Bad Host to OK Host. We have this running on a pretty beefy machine. The CPU Affinity for DST is CPU 1 - CPU 5 (5 total CPUs, DST is NOT on CPU 0) The physical amount of RAM on this machine is 72gb, DST has plenty of room to move around. We have 500mbps guaranteed throughput, burstable to 1gbps... network utilization was not even close to limits. The OS is Windows Server 2012 R2. I'll continue to monitor the server and generate profiles when I am able to. I have noticed that when I can handle about 10 players with pings that are lower than 100ms as an "OK Host" however if I have any player with a ping of over 150ms it can only handle about 7 players and becomes a "Bad Host". The players on the server were pretty awesome in helping me out and we tried a few different things... sticking together, spreading out, etc... and eveyrthing was about equal. When the high ping player dropped the rubber-banding stopped. Just some obervations, the high ping performance hit is something I have personally noticed on many occasions. Please continue to let us know if there is anything more we can do to help. DST_Profiler_Logs.zip