Maniaplanet Forum

Hi,

yep Haagse, i can report for Round Mode
On my 2 TM serv in Round Monde, CPU usage goes 1% to 99%
Then big Freeze...CPU return to 1% then quickly (3 mns) -> 20% --> 50 %--> 100% then again freeze.
After i downgrade
Players was 5/12 and 2/8, i was playing on 2/8 with a 'top' window running on the two serv.

Hope this help you
@+

New questions :
- What kind of hardware/OS is the server running on ?
- Have you tried the "NoLogs" exe ?

Gugli wrote:New questions :
- What kind of hardware/OS is the server running on ?

R710 / Dual Xeon 2.8 Ghz / 192 Go Ram / Network 2Gb in/out
Linux Centos 6.3 x64

First : the date mismatch is due to a mistake, but will not cause any trouble (apart from preventing to know the version currently running -_-')

Second : We believe we have found the problem.
The server writes a temporary log file for performance issues. On some systems, writing a file induces a lag, which means more data to write in the file, which means more lag... Hence the 100% CPU consumption
The bug is : these performance data were not intended to be written on disk, but in memory only.

As far as we know, it should not occur when using the NoLogs version. I fully understand that you're not willing to test it though. If you don't want to try maps with imported objects, I suggest you stick to the previous 1.3 release until someone else confirm that the NoLogs version works fine. Unfortunately, we have not been able to reproduce it on our servers, so we can not be 100% sure NoLogs versions solve the issue before someone test it.

We will fix that as soon as possible.

Thanks for your patience.

Intel Xeon i7 W3520
4x2(HT)x2.66+ GHz
Turbo Boost Technologie @ 2.93 GHz
Architektur 64 Bit
Ram 24 GB DDR3
Linux Ubuntu

I have a server with a self-build mode named "Hide&Seek". Its an new mode. But probably not what the cause is.

kremsy wrote: But why gives the Logs version not more Loggs than the 1.3???

The performance logs are not appearing in the standard output. They should not be written on disk at all : they should be kept in memory, and uploaded to us directly. Unfortunately, a temporary file is written, causing the bug.