Lags

Hello.

I got a problem with my server exe ...If 3 users online the server lags like hell how to fix this?It has notihng to do with GB ram cause my pc got engouth gb ram so how to fix this?Please help me my friend had this problem too he used then a other server exe and it worked but my server exe is to good and i dont like to use a other one
I hope this problem can be fixed... my server exe just can accept 3 users more not seems like

I hope anyone can help me to fix this


Thank You.^^

That (as I would expect from you) is a tricky question. I may try with a different server executable, and if the problem goes away, try to ascertain what the good server is doing that causes lag that the other one does't, to fix the good server in accordance with the fast server.

GBs RAM? Well... okay, here's the thing, 32-bit x86 code has a maximum address space of 2 Gig, it can page up to 4 Gig but can only use that under the Windows NT OS if your CPU supports PAE extensions. You cannot use PAE in Win x64, but your entire application is run in its' own 4Gig virtual x86 machine via WOW64 (Windows On Windows) since an x64 OS cannot run x86 code without virtualisation / emulation. But an x64 application on an x64 OS can address a couple of terrabytes of RAM.

There are memory instructions which can cause long delays in terms of CPU usage. During Paging, or accessing shared code in a different context (userland vs kernel space, supervisor mode or Ring 0, depending on your OS terminology) will cause context switches and level 1 and 2 cache invalidation as well as a great deal of work for the MMU, just from a single CPU instruction.

2 different implementation of the same thing do not necessarily perform the same. So when you compare the two server executables, check for page faults, CPU use and Memory use, as well as how much of that memory is actual and how much is virtualised in the pagefile.

It won't be easy at all, but I suspect that if you can muster the patience you may be one such person here who may be able to make sense of it.

I wish you the best of luck.

like bobsbol said its a tricky question.
try not log in from the host pc..and its not just about the ram.
and the internet connection effects too..under 2.5mb of speed you will lagg like hell..like u said

Well, if it was a matter of bandwidth, I suspect it would matter what the players where doing, not just how many of them are logged in... as we discussed in another thread Imri.

If the lag is caused as soon as the user count increases above a certain point, some resource is running short.

It is possible, within a server to force or deny Virtualisation of memory resources (to the swap / page file) and page faults cause massive system lag, depending on your IO architecture. It's less noticeable on a server with server specification SCSI RAID with decent DMA allocation, which usually precludes you from having a DMA soundcard or Accelerated Video card. You don't need those on a server; you do need fast drive access.

But it's about balance in the performance in the machine. I always say that a JCB is as powerful as a Racing Car, but the power is used from something completely different. It's that same thing with Servers vs. Gaming PCs. Same engine, totally different emphasis on the application of that horsepower, and you can't make a Racing Car that can dig trenches and lay roads like a JCB, or a JCB that can win a Race... You have to make the choice.

It is possible to optimise your code for a specific hardware set though. I guess the equivalent is Race Fuel to industrial Diesel.

RAM is usually pretty fast, but if you run out of it, an indexed file is quicker than a page fault, because a page fault kicks in a JIT Debugger in the Kernel which then swaps memory out to disk and disk information into memory and then returns to executing your program... If your program handled the situation it's self, that would be quicker... but if it didn't need to (because you have enough RAM to cope without any faults) the memory handling code would waste valuable CPU time.

It's also possible you get error return packets with one server and not the other using a particular client... that will clog the network bandwidth up with Error and Resend packets whatever players are doing.

Watch drive access times. If you keep your configuration on a CF Disk, it will start really fast. But if you keep your database on a CF, every SQL access will be really slow... why? CF is a very fast read medium, and a very slow write medium.

Similarly many early guides told you to place your swap file on a different partition to the game server and it's database. Reduce contention.

Whatever the issue, you need to find what it is that this specific server is trying to do that your system isn't up to achieving. You know your system is capable, because it doesn't present the same issue with another server exe... so it's just some resource that the problem one is hogging.

tr1pl3x here is full explainition.
nothing more to say.
thanks bobsbol