Open Krycek-dk opened 10 years ago
@JB88 and @Jay13 please see this one.
@Krycek-dk
Ill make this a priority, however this appears to be a pre 3.0 issue, more like a post "win" patch from BIS.
@Jay-13
I´m afraid that everything is not related to the latest patch, but i´ll sure appreciate you taking a look at it mate. :+1:
The info about these _Object not found_ issues is very sparse / non-existent.
@Krycek-dk
Ok so ive looking the coding over and I still cant find anything thats causing a recurring search for items which is whats slowing us down. Its been suggested to me however, that the revive script can lead to multiple items listing as in game when they are not to be found, which would explain the weapon glitch?
@Jay-13
Thx for your attempt mate. I also had come to the same conclusion, that it is probably the Revive Addon that is causing some of all this mayhem. Therefor I have been spending a lot of time cleaning it up today and it's already starting to works much better. I even believe I have fixed Issue #26 :)
Believe I have found what is causing this. :D Will fix it tomorrow and report back! :+1:
Super important issue!
The server is suffering hard after the 3.0.0 update. At this point I really don't have any clue as to what exactly is causing this, but I will give my right arm to figure it out! I have hear that some of these "not found" logs, posted below, could be related to something with setPos, but i´m sure that is not entirely the reason for this insane log spam.
Anyways, this server performance issue, is most likely due to the server log (.rpt file) being super spammed with stuff like:
Note: the "_x_" is various different numbers.
The following is my Gist upload from a cutout of a 50.000 lines rpt. file as a "small" example! Worst file we got is over 2.8 million lines and over 150MB in size. :o arma3server_2014-03-31_18-00-23.rpt So the issue gents is very serious and the server FPS is getting as low as 1 (server side) at times or rather after it has been running for a long time.
Here is a quick screenshot from our Server Monitor. This is only after the server has been running 2½ hours! :(