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.
Vultr CPU by Locations
I see some comments about vultr 'poor' cpu's and i created vms on all locations to see difference. ( Performance Series 1CPU/1024MB )
So.. i always use Paris location and always have this configuration(3600MHz). I guess this is standard cpus/zone.
== London, Paris, Australia, Dallas == <4>
model name : Virtual CPU e7da7129d3ee
cpu family : 6
model : 60
cpu MHz : 3600.014
cache size : 4096 KB
bogomips : 7200.02
== Silicon Valley, Miami, Los Angeles, Seattle, New Jersey, Chicago, Amsterdam, Atlanta, Tokyo, Sydney == <10>
model name : Virtual CPU e7da7129d3ee
cpu family : 6
model : 60
cpu MHz : 2399.996
cache size : 4096 KB
bogomips : 4799.99
Comments
This doesn't mean much. It's "cloud" and they've the capability to live migrate VMs to different host nodes, even across different data centres if need be. Some locations will have varying configurations, some locations could even be moved over from ~3Ghz to ~2Ghz CPUs.
If you want dedicated CPU configurations, go dedicated. Many reputable hosts will live migrate customer VMs from varying hardware configurations to manage loads, deal with EOL hardware etc. I know specifically that AWS and BigV do it.
@kcaj, true.. but now this configurations are available. That's ugly to change specs of already created VMs, vultr do this? You have servers on vultr which downgraded from 3Ghz to 2Ghz?
So for australia location i get 3.6 Ghz CPU Speed ?
NOW, yes.. later idk