DayZ Network set-up (Quack, you maybe know about this?)

[MikeGracia]

Hey guys, I have a 3 core VDS that runs DayZ pretty well. We don't get that many players usually, btu I am about to do a promo/push (forums, YouTube etc).

For that reason, I wondered about any configs I can do to the DayZ server, and/or the Windows set-up. I wish I had funds for an extra core, or even an extra MySQL host, but I don't, so just trying to optimise what I have got! - What I am wondering:

Setting Windows to favour background services, or programmes - Which will work best? (I amready have Arma2 start as high priority via a batch file I use for reboots, but not sure whether telling Windows to favour background or programmes is best?)

Any other Windows configs?

This is perhaps a biggie - In the '\Arma 2 Operation Arrowhead\dayz_1.chernaruszbasic.cfg' file, I have the following, btu am not sure how to optimise it for my server - I say a thread over on dayzmod forums - but it's quite old, and many people disagree with some of the stuff!

Anyone here know if the following could do with Tweaking?

Code: Select all

MinBandwidth=104857600;
MaxBandwidth=1073741824;
MaxMsgSend=128;
MaxSizeNonguaranteed=256;
MinErrorToSendNear=0.029999999;
MinErrorToSend=0.003;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_Bpp=32;
class sockets
{
	maxPacketSize=1400;
};
serverLongitude=2147483647;
serverLatitude=2147483647;
serverLongitudeAuto=2147483647;
serverLatitudeAuto=2147483647;

Last question... TCP optimizer? I've seen a few folks talks about this - any point in using the programm people go on about?

Thanks and beans in advance!

Mike.

[kraze]

For the most part your rates are fine and are similar to what I've suggested to other users running DayZ.

If I remember correctly TCP optimizer won't help you since DayZ uses UDP. I believe it is just the communication from the server to the hive that is TCP. However, it won't necessarily hurt to run it.

Leaving the Windows setting to background services should be fine but you may want to play around with both settings and see if one can offer slightly better performance.

Are you actually seeing issues with your server or are you just proactively attempting to optimize?

[.=QUACK=.Major.Pain]

We run the default settings for the basic.cfg on all our servers and we have been fine with that.

Location of server is mostly where you should concentrate on for connection issues.
We have a New York and Seattle dedi server and Seattle had a lot of issues in the beginning, but the data center found a faulty cable causing a lot of packet loss. Now it's just the overloaded connections from easy coast to west coast that are a bigger concern.

Stick to a more central or eastern location would totally cut out that issue if your gang is more to the east.

We dropped the New York even though it was flawless and stuck with the Seattle since they were almost the same servers but for almost half the price.

[Edge100x]

To clarify, Pain's talking about a lower-end provider, it seems. We have not experienced notable hardware or routing problems at any of our locations (no faulty cables or cross-country routing issues). Sometimes individual clients do experience routing problems, and if you have a player see one of these, please submit a support request to discuss it, as InterNAP can often route around such problems. Since latency has a large component based on distance, locations that are closer to a client will usually also have lower latencies.

While we also have low prices, our main focuses here have always been performance, service, and overall quality.