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.
Comments
check out this site http://www.binarytides.com/linux-cpu-information/
Run ServerBear on each vps and post the outputs please. http://serverbear.com/
@SkylarM ,
http://my.crissic.net/ is
403 Forbidden, consider301 Permanently Movedto HTTPS.hi, i get full frequency
node : jax06
@century1stop
I got a reply from support. No resolution yet. I tried rebooting multiple times, and have reinstalled the OS multiple times within the past 48 hrs.
isn't os related and processor info is on 2nd processor, not 1st. Issue may be with 1st processor (processor: 0 - 11)
Is it affecting the performance of the VPS? Run a server bear on both and see.
I'm in the process of doing that right now.
5 bucks say performance will be affected
Yeah. I am 100% sure it effects performance because the vps with the higher mhz completed the centminmod install around 6 minutes faster than the other.
Serverbear is currently doing "Running FIO test", which is taking quite a long time.
Ryan is offering to move the VPS to a different node, going to wait for the serverbear reports first.
Did you order them at the same time, have they checked the CPU settings in SolusVM to make sure one does not have a different CPU restriction than the other plan. Maybe an older plan where they have since changed CPU settings since ordering second?
They were ordered during the same promotional period. It's their $15/year with 2ipv4 plan from a long time ago.
I will ask them about the cpu restrictions.
huge difference in unix bench. 877 vs 2143, but the results don't make much sense to me. The one with the lower unix bench score has a higher io speed.
vs
It don't make sense. Just follow what they said in the support ticket to migrate to another node to see what happens.
I agree with @aggressivenetworks
Move it to a separate node, at least you get the added benefit of node redundancy should you ever need it
Seems like both nodes might have issues, but different ones.
I'd share the results to the provider and let them have a look at it.
They might be able to improve circumstances on those nodes and help you out.
Both of those VPS's are on the same node. I asked to be moved to a different node but they haven't answered the ticket in the past few hours.
I'll look into it.
As far as the CPU frequency issue, that's an old issue in relation to VPSMON, which we no longer use. It used to limit CPU. We can manually fix your CPU rating by editing your container config and restarting it.
Updating this thread.
Issue is finally resolved.
They migrated me to a different node but that didn't fix the issue.
Then Skylar found the problem.
Everythings back to normal now
so what was the problem?
An incorrect setting in the containers config file as stated earlier in the thread.
Hmm, I wonder if they have any other customers that have the same issue but are unaware.
duh, same node
which file setting please? like to go through it
https://openvz.org/Man/vz.conf.5
Look at VE0CPUUNITS
it isn't related to processor frequency, just base cpu unit setting, regardless how many cpu units you have frequency should be the same. anyhow, both vps on the same node, so based on vz.conf, they can't differ
look at the bright side. if we are able to nail the issue here, it will benefit both provider & OP plus everybody else, the intent is to get a solution, not crucify.
You can set limits per container.
even on auto provision? limits or frequency?
That was not from provision, i think it was from an automated tool they used to limit abusers automatically. When they stopped using it, the configs were not reset per container, i think.
should not affect cpu internal frequency, nevertheless