Which version of Windows for a VPS

[PDC]

One of my New Years resolutions has been to start on some automation and I want to run it on a VPS.

I have been looking at VPS providers and most of the ones I am looking at offer 4 different options for the Windows operating system:

Windows 2019 Standard (64 bit)
Windows 2016 Standard (64 bit)
Windows 2012 R2 Standard (64 bit)
Windows 2008 R2 Standard (64 bit)

The pre-selected option is Windows 2008 R2 Standard (64 bit) but as that is over 10 years old I wondered if that is the option I should stick with or is it better to go with one of the others and what are the differences/potential issues?

I have tried to search the forum for the answer but couldn't find it.

[Euler]

I haven't used 2019 yet, but all mine are on 2016 and I haven't seen any problems.

[ShaunWhite]

Windows 2012 R2 Standard (64 bit) is the best choice imo. Lightweight and does the job.

Peter, what does 2016 (and 2019) do for you that the others don't?

[PDC]

Thanks both for your replies, it sounds like either the 2012 or 2016 versions have been fine for both of you so I will probably opt for the 2016 version as that is the most recent tried and tested version.

[ShaunWhite]

Thanks both for your replies, it sounds like either the 2012 or 2016 versions have been fine for both of you so I will probably opt for the 2016 version as that is the most recent tried and tested version.

I see the logic but it differs from mine. Newer versions have all new issues perhaps yet undiscovered and certainly with less info about them on forums. Older versions are extremely well tested and patched and discussed. Newer versions are also bloated with additional features, often irrelevant to my implementation. Often unless code if code written for an older version is patched for the newer versions they execute slower too because of the translations required. You takes your pick though, probably no bad choice, but I'm not seeing any comments that say newer is better because.......I mean, just look what a nose dive new windows versions have been, the best was probably xp which 'died' years ago.

[PDC]

I haven't used 2019 yet, but all mine are on 2016 and I haven't seen any problems.

With a few days off due to the lack of racing I have gotten around to getting the VPS with Windows Server 2016 Standard (64 bit).

Are there any settings that are worth turning off/changing in Windows that anyone can recommend in order to optimise the performance?

For example are there any display settings worth turning off as I don't need any fancy shadowing of windows but rather the basic views.

Many thanks.

[Dallas]

I haven't used 2019 yet, but all mine are on 2016 and I haven't seen any problems.

With a few days off due to the lack of racing I have gotten around to getting the VPS with Windows Server 2016 Standard (64 bit).

Are there any settings that are worth turning off/changing in Windows that anyone can recommend in order to optimise the performance?

For example are there any display settings worth turning off as I don't need any fancy shadowing of windows but rather the basic views.

Many thanks.

I'd recommend using a program like NetTime to keep your VPS clock right, especially if using automation from it
http://www.timesynctool.com/

[ShaunWhite]

I'd recommend using a program like NetTime to keep your VPS clock right, especially if using automation from it
http://www.timesynctool.com/

I haven't seen that one so I'm not sure what it does but you can also add a daily task to run "c:\windows\system32\w32tm.exe /resync" to your TaskScheduler to force a resync.

If you need to syncronise across servers you can then set up another task to run the WS2012 TimeSyncronisation feature (sc.exe). Chances are you won't though as syncing two seperate servers to world clock shouldn't give you more than about 50ms difference and that's close enough.

sc.exe exists for when you need multiple servers bang in sync, we only ever used it when syncing servers that were attached to different liquidity pools and needed microsecond sync, but I'm going back almost 20yrs so that's a bit fuzzy. My bro-in-law says he syncs to nano seconds these days. I asked him how and he wouldn't tell me I'm pretty sure that I'm not a threat to his outfit, but rules are rules I guess and he's a buttoned-up company guy.

[jimibt]

I'd recommend using a program like NetTime to keep your VPS clock right, especially if using automation from it
http://www.timesynctool.com/

I haven't seen that one so I'm not sure what it does but you can also add a daily task to run "c:\windows\system32\w32tm.exe /resync" to your TaskScheduler to force a resync.

If you need to syncronise across servers you can then set up another task to run the WS2012 TimeSyncronisation feature (sc.exe). Chances are you won't though as syncing two seperate servers to world clock shouldn't give you more than about 50ms difference and that's close enough.

sc.exe exists for when you need multiple servers bang in sync, we only ever used it when syncing servers that were attached to different liquidity pools and needed microsecond sync, but I'm going back almost 20yrs so that's a bit fuzzy. My bro-in-law says he syncs to nano seconds these days. I asked him how and he wouldn't tell me I'm pretty sure that I'm not a threat to his outfit, but rules are rules I guess and he's a buttoned-up company guy.

Shaun -or a server, you might want to follow this little guide (same as you have above, but full details): https://www.pretentiousname.com/timesync/

altho things won't drift much in a 24 hour period, setting this to sync at 12:00 daily seems more than resonable to ensure alignment with UK racing etc..

[PDC]

Thank you for the replies.

Is there some underlying issue with the clocks on VPS as I don't have to sync my desktop PC's clock ever and it always seems to be in sync with the actual time.

[jimibt]

the clock is synced by a windows service once a week by default. the rationale here is to ensure that the clock is up to date bang in front of the trading session. the clock CAN and DOES slip by varying amounts across 7 days (even if only a few seconds over that time period!)

[Dallas]

I just checked my net clock log on the VPS which re-syncs every 15mins
During that time on average it drops out around 20ms-30ms with a few entries as high as several hundred ms

[jimibt]

I just checked my net clock log on the VPS which re-syncs every 15mins
During that time on average it drops out around 20ms-30ms with a few entries as high as several hundred ms

if left for a week, that would be about 2-3 minutes - whao!! certainly worth recalibrating regularly then. I thought once a day was fine

[Dallas]

I just checked my net clock log on the VPS which re-syncs every 15mins
During that time on average it drops out around 20ms-30ms with a few entries as high as several hundred ms

if left for a week, that would be about 2-3 minutes - whao!! certainly worth recalibrating regularly then. I thought once a day was fine

Those larger entries were few and far between but even just working an average of 25ms every 15mins that's still around 2.4secs a day if left which isn't ideal when running automation and gathering data

[PDC]

I just checked my net clock log on the VPS which re-syncs every 15mins
During that time on average it drops out around 20ms-30ms with a few entries as high as several hundred ms

Are you able to check that log in the program you recommended Dallas, Net Time? Or are you looking somewhere else?

I am surprised the time slips that much, over the course of a week that is significant slippage.