02-21-2021, 12:58 PM
(06-11-2020, 01:53 PM)ikk157 Wrote: It specially caught my attention that you mentioned that Deanhills informed you that the previous holder of VPS 9 Seattle had negative feedback on it (never knew that to be honest). That, if anyone here doesn’t already know, is the same VPS i had currently.
I have to say that you're wrong!.. and here is why?
You and the previous VPS older are both located in Seattle, but ever since the transition to KVM, your KVM VPS has nothing to do with @Golden's OVZ-based VPS 9 Virmach Seattle.
So, whatever issue you have has nothing to do with his own sets of problems. i've just checked that review and it looked like a misconfig of the VPS from the start:
Code: (Select All)
System Info
-----------
Processor : Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz
CPU Cores : 2
Frequency : 2401.000 MHz
Memory : 8192 MB
Swap : 0 MB
Uptime : 16:28,
OS : Ubuntu 14.04.5 LTS
Arch : i686 (32 Bit)
Kernel : 2.6.32-042stab127.2
Hostname : Post2Host-SeattleStarting from using a 32Bit OS template (on a 64Bit VPS host!!) but recognizing 8GB RAM nevertheless, which point to the possibility of PAE being enabled.
Just from this fact alone, I would say that the OVZ-based Seattle VPS-9 needed a 64-bit template re-install from the get go.
And if you pay attention to that OVZ VPS host's processor, you would note that it was an Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz, while your own KVM-based Seattle VPS has : Intel® Xeon® CPU E5-2670 v2 @ 2.50GHz.
Conclusion: It's not even the same VPS host that's used, let alone the fact that an OVZ-container has nothing to do with a KVM-VM performance-wise when running inside the same VPS host!