Tremded on a virtual server: advices requested...

[codernem]

Hello everybody,

Briareos and I are currently running a couple of tremulous servers (ProlinuxNG and Prolinux GPP) on our VPS (Virtual Private Server). However, we are not satisfied of our provider, and we are going to change. Speaking with Napkin few days ago, he was astonished about being able to successfully run a tremded process on a virtual machine, and he suggested me to ask the developers about what kind of issues this can eventually have.

So, before wasting other money ... Is there any known issue about running a tremded process on a virtual machine (basically, a machine virtualized using XEN or Virtuozzo or VMWare technologies) ?

Thank you for your time

[kevlarman]

the main issue is that it may or may not work (well), and you have no way of knowing whether it will or not until you try. the problem you should be looking for is ingame timers being screwed up (easiest way to test is to build something and see how long it takes your build timer to count down, and compare that to a local server running the same code. if it differs by more than a second, find a new host). if you look for something with relatively low contention ratios, it should be pretty safe though.

[Lakitu7]

As I understand it the problem comes in CPU load conditions. When there's not enough cpu to go around, the way a regular OS handles it is different from the way the VM system distributes cpu-time to each VM. As such, I believe you're fine if a) the cpu on the (physical) box is not overburdened and never will be b) the cpu is essentially not being virtualized at all, which probably won't be the case in any large-scale commercial setup. But even if those are true, I guarantee nothing

[codernem]

Thanks a lot, guys

[Silver]

For what it's worth I ran a trem server on a godaddy vps for about 2 months.  It ran decently but most people seemed to have a lot of latency issues.(Godaddy really sucks on connection aspect but their hardware was acceptable)

[Kiwi]

As I understand it the problem comes in CPU load conditions. When there's not enough cpu to go around, the way a regular OS handles it is different from the way the VM system distributes cpu-time to each VM. As such, I believe you're fine if a) the cpu on the (physical) box is not overburdened and never will be b) the cpu is essentially not being virtualized at all, which probably won't be the case in any large-scale commercial setup. But even if those are true, I guarantee nothing

I agree with you, but I believe certain VM programs give you the option of how you want to split up your resources, and wether the VM or your computer get first pick.  Although I do think your right, because that is how most VM programs work, from my understanding.

Best Regards,
Kiwi