New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Hetzner vServer CX50 review? Is it good? Any benchmark?
Hello,
Is this vServer good?
https://www.hetzner.de/hosting/produkte_vserver/cx50
About uptime,performance,network?
Is there any benhcmark about cpu performance?
Thanks
Comments
I have a CX10 if you want some benches from that
if you could rund this i will be very happy
https://freevps.us/downloads/bench.sh
Thank you if possible!
Not the same guy but I also have a CX10. Here's my results:
Here's also cpuinfo:
and
openssl speed -evp aes-128-cbc
:Thanks , but finally i am with netcup.de
It's a ipv4 NAT KVM vps now?
(ref https://wiki.hetzner.de/index.php/VServer/en#Why_does_my_VM_have_the_IP_172.31.1.100.3F)
Sounds like the online.net setup
depends how you'd define that ;-) those CX boxes get their own dedicated IPv4 address.
but they are connected more like a routed setup so your VM has an internal IP in its network config which forwards 1:1 from and to the external IPv4.
Anyone can elaborate on what could be the reasons for this setup and which pros / cons it has compared to directly assigning the IPs to the VMs?
as I am not so familiar with network setups used in DCs I can only try and make an educated guess ;-)
if I am not totally wrong to set up virtual machines you could either assign smaller subnets to the hostnodes but will loose usable IPs for gateway and broadcast and such.
or use some sort of bridged setup where you have to add virtual mac adresses for every single IP and assign that vmacs to the VM.
this may come with some more effort in doing so, at least automatically, as this may involve more systems than the hostnode itself (router perhaps) ...
so easiest way may be routing all IPs in question just to the hostnode which then simply sets a static route to the VM.
that VM internally gets a private IP assigned as endpoint of that route.
so no need to use extra IPs for gateway and broadcast etc and probably most of the setup can be done on the hostnode directly.
Dont forget about the added bonus of easy migrating. Just need to re-route the internal address, maybe even change it, but keep the external one. No need to move subnets between nodes and whatnot
Those cx50s would be good value as local memcache considering hetzner's current serverbidding rates.
OK. My reading comprehension was imaginative in an ultra-sleep-deprived state.
Correction: It DOES have public IPv4.
Currently the private IP is the same for all: 172.31.1.100. The public IP is displayed in the Robot.
OK. My reading comprehension was imaginative in an ultra-sleep-deprived state.
Correction: It DOES have public IPv4.
Currently the private IP is the same for all: 172.31.1.100. The public IP is displayed in the Robot.
More detailed : http://serverfault.com/questions/725255/cant-use-external-ip-on-hetzner-vps/773897#773897