1. What's the cpu, memory and network utilization in the last 3 hours?
     
  2. Have you got a logiciel for seeing my stats in graph because i am in nitrado host :/
     
  3. Nope I don't
     
  4. I got the same problem and my CPU is stable at 11%, RAM at 13% and network 1.77%. What do you think @Hatemail ?

    EDIT:
    This is the average over the last 3 hours.
     
  5. what is your host ?
     
  6. Hi,

    I don't know why but my console is flooding this.
    Code:
    TimeWarning: Steam.QueryRespond took 0.11 seconds (114ms)
    TimeWarning: Net.sv.Cycle took 0.10 seconds (102ms)
    TimeWarning: Steam.QueryRespond took 0.17 seconds (165ms)
    TimeWarning: Net.sv.Cycle took 0.19 seconds (191ms)
    TimeWarning: Steam.QueryRespond took 0.26 seconds (264ms)
    TimeWarning: ServerMgr.Update took 0.51 seconds (513ms)
    TimeWarning: AIHandler.Cycle took 0.42 seconds (424ms)
    TimeWarning: Steam.QueryRespond took 0.15 seconds (152ms)
    TimeWarning: ServerMgr.Update took 0.60 seconds (595ms)
    TimeWarning: Net.sv.Cycle took 0.16 seconds (164ms)
    TimeWarning: Net.sv.Cycle took 0.14 seconds (142ms)
    TimeWarning: Steam.QueryRespond took 0.11 seconds (113ms)
    TimeWarning: Net.sv.Cycle took 0.15 seconds (151ms)
    TimeWarning: Steam.QueryRespond took 0.15 seconds (149ms)
    TimeWarning: Steam.QueryRespond took 0.27 seconds (267ms)
    TimeWarning: Net.sv.Cycle took 0.16 seconds (162ms)
    TimeWarning: Steam.QueryRespond took 0.14 seconds (137ms)
     
  7. Hi. I'm wondering if these messages are related to the issue? I'm getting these alot in my console:

    Code:
    TimeWarning: AIHandler.Cycle took 0.12 seconds (116ms)
    TimeWarning: Net.sv.Cycle took 0.11 seconds (108ms)
    TimeWarning: BasePlayer.ServerCycle took 0.11 seconds (112ms)
    Edit: I do not have Cornucopia.
     
    Last edited by a moderator: Sep 20, 2015
  8. Make sure to have your server fully updated, including oxide. The error your having could have been a cause by Rust, double check, and see if that fixes it.
     
  9. Problem too!
     
  10. I have this too........
     
  11. I have it too. according to many players, is that on many servers
     
  12. Long story short is told in header. During the events that shown below server FPS drops from 240 to 10 and it repeated very often. Can anyone help to solve this problem? It appeared after heli update.
    Code:
    TimeWarning: AIHandler.Cycle took 0.25 seconds (252ms)
    TimeWarning: ServerMgr.Update took 0.53 seconds (533ms)
    TimeWarning: AIHandler.Cycle took 0.23 seconds (234ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (250ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (254ms)
    TimeWarning: AIHandler.Cycle took 0.18 seconds (177ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (249ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (249ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (249ms)
    TimeWarning: playerattack took 0.26 seconds (263ms)
    TimeWarning: Net.sv.Cycle took 0.27 seconds (269ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (242ms)
    TimeWarning: ServerMgr.Update took 0.52 seconds (523ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (243ms)
    TimeWarning: AIHandler.Cycle took 0.26 seconds (257ms)
    TimeWarning: AIHandler.Cycle took 0.26 seconds (256ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (242ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (243ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (238ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (248ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (253ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (249ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (250ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (254ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (250ms)
    TimeWarning: AIHandler.Cycle took 0.26 seconds (256ms)
    [Oxide] 5:16 PM [Info] [BetterLoot] BetterLoot: Refreshed 3 containers (0 destroyed)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (238ms)
    TimeWarning: AIHandler.Cycle took 0.15 seconds (147ms)
    TimeWarning: AIHandler.Cycle took 0.26 seconds (263ms)
    TimeWarning: AIHandler.Cycle took 0.25 seconds (251ms)
    TimeWarning: AIHandler.Cycle took 0.15 seconds (154ms)
    [Oxide] 5:16 PM [Info] [BoxLooters] BoxLooters: Data saved!
    TimeWarning: AIHandler.Cycle took 0.26 seconds (262ms)
    TimeWarning: AIHandler.Cycle took 0.24 seconds (244ms)
    TimeWarning: AIHandler.Cycle took 0.18 seconds (176ms)
     
  13. I don't know if you can solve it, I think its a problem with the programming of the vanilla rust server.
     
  14. I have two theories on that one, but I have yet to confirm.

    First off, some facts, this bug wasn't around until a couple weeks ago and it showed up before the heli update I'm 100% sure. Others have mentioned the new decay system and I think this really is a sound theory. Obviously the new decay system is more complex and would require more processing time. Why exactly it would show up in the AI cycle is a bit of a mystery for me though!

    Another important fact here is that if you remove ALL animals from the map, the problem goes away and will come back once a certain amount of them show up. Also very important to note is that as a server "ages", that time increases. Again, this points to the decay system as logically, an older server will have more structures and thus more decay processing to do.

    Another theory I have though is those animals that get stuck with pathing issues... You know those animals that just wiggle left and right and can never leave their spot because of rocks around them? I'm wondering if these guys are not wasting CPU time by going too deep in some recursive loop to try and find a path. I've actually wanted to make a feature in Cornucopia to check for these and delete them when they are detected... I might do that to test the theory out.

    The decay system is the most likely culprit though, I just don't see how it's tied with the AI cycle... doesn't make sense but I didn't look at the decompiled code for that area so maybe Decay is batched in that call, I dunno.

    I wiped my server last night and I don't have these anymore, for now...
     
  15. The problem could probably be solved by not letting the animals move at all if nobody was near. I don't think its worth the cpu cycles, imo.

    But truly, I think the whole server software is beyond hope since it uses about 50% cpu without anyone being on at all.
     
    Last edited by a moderator: Sep 23, 2015
  16. Same here, all is taking too many ms!
     
  17. Same for me, server just wiped, 50k entities and have this.
     
  18. Code:
    (17:34:18) | TimeWarning: rpc_opendoor took 0.08 seconds (83ms)
    (17:34:18) | TimeWarning: Net.sv.Cycle took 0.33 seconds (327ms)
    (17:34:34) | TimeWarning: ServerMgr.Update took 1.13 seconds (1129ms)
    (17:36:14) | TimeWarning: rpc_opendoor took 0.08 seconds (80ms)
    (17:36:16) | TimeWarning: rpc_opendoor took 0.06 seconds (62ms)
    (17:36:17) | TimeWarning: rpc_opendoor took 0.08 seconds (79ms)
    (17:36:17) | TimeWarning: Net.sv.Cycle took 0.20 seconds (201ms)
    (17:36:18) | TimeWarning: sv_requestfile took 0.08 seconds (80ms)
    (17:41:04) | TimeWarning: ServerMgr.Update took 82.47 seconds (82470ms)
    Can someone help me to understand ?

    explanation of my provider : ( french )
    [17:50] <@VG|DaskaR> C'est une légére pertubation sur le disque de la machine, nous allons corriger le problème.
     
    Last edited by a moderator: Sep 24, 2015
  19. Starting now on my server :
    (17:34:34) | TimeWarning: ServerMgr.Update took 1.13 seconds (1129ms)
    (17:36:33) | TimeWarning: Net.sv.Cycle took 0.39 seconds (387ms)
    (17:41:04) | TimeWarning: ServerMgr.Update took 82.47 seconds (82470ms)

    explanation :

    [17:50] <@VG|DaskaR> C'est une légére pertubation sur le disque de la machine, nous allons corriger le problème.