All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
does your VPS experience lost time (stalls) - test it
If you are in a container on an overloaded node try this one liner in your console and watch it for several minutes.
You are looking for more than one second apart in the time on the left.
vmstat 1|while read x;do printf "%.12s $x\n" "$(date +%T.%N)";done
(needs procps and coreutils which you should have, otherwise use apt-get, yum, etc.)
don't be confused by the hundredths, I added that so you can see how "on the nose" vmstat and bash are outputting the line, losing a few tenths or hundredths is fine
reminder: problems usually won't show up immediately, you have to watch for minutes
my own results so far:
OVH kvm - loses time even when container is completely idle, up to 8 seconds!
VMbox openvz - so far so good, sometime loses tenth but never a full second
Ramnode SKVM - smooth as silk, doesn't even lose tenth of a second
about vmstat
the first column "r" is the runqueue, which is number of tasks running or waiting to run - if it is mostly zero, your container is mostly idle
the second column "b" is the blockedqueue, which is stuff that is waiting and cannot be interrupted - it should nearly always be zero or it means you have slow I/O (slow disk)
Comments
Even on a node with 100% CPU usage and fairly high iowait simulated in a few containers I get this:
@linuxthefish - it should be observed for a few minutes (disk cache writes and all that) but good to see
is that running from a container or the parent node? because the r (runqueue) is almost always zero which means there are more cpu cores than tasks running
All Vultr locations, looking good
@Fusl your "r" value is also mostly 0 so be sure to watch it for a few minutes
(that's a whole bunch of containers!)