Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
25% Recurring Discount on NVMe VPS
Try EnsoVPN - Reliable VPN - 1-Day Free Trial
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
Try EnsoVPN - Fast & Private VPN - 1-Day Free Trial

Categories

In this Discussion

Home › General
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.

GreenCloudVPS issues

q2836400482q2836400482 Member
in General

How are GreenCloudVPS servers? Are they stable for hosting websites? I’ve heard they have very strict CPU limits—apparently, running a single benchmark test can get your server shut down.

Comments

  • hatebreederhatebreeder Member

    Currently have a yearly paid server from 22nd October 2025.
    Minimal downtime, Very stable. Simply no problems.

    Thanked by 1NDTN
  • JohnFilch123JohnFilch123 Member
    edited July 17

    I have heard that GC has got strict CPU limit and once one of my servers was suspended for high traffic but a ticket quickly fixed it. Otherwise, all good, never had any issues.

    Thanked by 4NDTN oloke buggedout forest
  • hennaboyhennaboy Member

    30% as stated in their terms.

    Never had a problem I have 6 servers with them.

    Thanked by 2NDTN oloke
  • suutsuut Member

    They also have VDS.

  • NDTNNDTN Member, Patron Provider, Top Host

    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Thanked by 26oloke JohnFilch123 sliix khalequzzaman nick_ david hatebreeder Nekopara ScreenReader barbaros nghialele host_c sbenchid NotFoundException hennaboy FAT32 DrNutella lichade themew Xrmaddness JohnnySac buggedout cybertech Pwner DanSummer Ganonk
  • NotFoundExceptionNotFoundException Member

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

  • lowendclientlowendclient Member

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    I have a suggestion: allow users to cap CPU usage at qemu via ticket, to help prevent website suspension during high traffic periods (days).

    Thanked by 1forest
  • hennaboyhennaboy Member

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Thanked by 1NotFoundException
  • yokowasisyokowasis Member

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

  • hennaboyhennaboy Member

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    Thanked by 1DrNutella
  • DrNutellaDrNutella Member

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    I like to stir bowl. It gets messy quick. Pots are clean ways to stir.

  • resultfbresultfb Member

    In my experience, from several providers, it's not that strict, they only enforce bandwidth limits, you can pay for bandwidth equivalent to half a year of your VPS cost. The really strict one is Hostdzire's Leaseweb product, they use cpusteal for limitation.

  • eloftyelofty Member

    Just buy enough cpu or a VDS with dedicated resources, simple.

  • Mik3y326Mik3y326 Member

    I have a VPS from 2024, never had any issues. To be honest, I dont really use this VPS except for the occasional yabs like every 1 or 2 months. Done that for the past 2 years, have not been suspended yet :wink:

  • yokowasisyokowasis Member

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    Actually Yes.

    Thanked by 1rpqu
  • usuariomegausuariomega Member

    A quick question: is that 30% CPU usage overall for instance, just 30% user time, or the total CPU usage?

    If I'm uploading a file and the disk is slow, causing 95% iowait, will the VPS be shut down?

    Example 1:
    17:00:00 CPU %user %nice %system %iowait %steal %idle
    17:10:02 all 10,00 0,00 1,00 20,00 2,00 67,00

    Example 2:
    20:00:00 CPU %user %nice %system %iowait %steal %idle
    20:10:28 all 1,05 0,00 3,19 95,75 0,00 0,00
    20:20:54 all 1,00 0,00 3,05 95,94 0,00 0,00

  • VTCuongVTCuong Member

    @usuariomega said:
    A quick question: is that 30% CPU usage overall for instance, just 30% user time, or the total CPU usage?

    If I'm uploading a file and the disk is slow, causing 95% iowait, will the VPS be shut down?

    Example 1:
    17:00:00 CPU %user %nice %system %iowait %steal %idle
    17:10:02 all 10,00 0,00 1,00 20,00 2,00 67,00

    Example 2:
    20:00:00 CPU %user %nice %system %iowait %steal %idle
    20:10:28 all 1,05 0,00 3,19 95,75 0,00 0,00
    20:20:54 all 1,00 0,00 3,05 95,94 0,00 0,00

    1. 30% overall average usage of the instance in the last 24 hours.
    2. The iowait metric does not count, as the kernel still able to allocate it for other tasks. Though you wouldn't get that kind of terrible performance from them, they're the Top Provider™ for a reason :wink: .
    Thanked by 1oloke
  • usuariomegausuariomega Member

    @VTCuong said: The iowait metric does not count

    So, you mean it's just the %user—the 30% average over 24 hours?

    Thanked by 1mexyul
  • forestforest Member

    @usuariomega said:

    @VTCuong said: The iowait metric does not count

    So, you mean it's just the %user—the 30% average over 24 hours?

    Also system, since iowait does not use the CPU.

  • cybertechcybertech Member

    i regularly run YABS with no issues.

  • totototototo Member

    @cybertech said:
    i regularly run YABS with no issues.

    * * * * * curl -sL yabs.sh | bash

  • hennaboyhennaboy Member

    @yokowasis said:

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    Actually Yes.

    Content not available

    But at a guess it sucks to suck.

  • yokowasisyokowasis Member

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    Actually Yes.

    Content not available

    But at a guess it sucks to suck.

    https://imgur.com/C0P5ZKQ

    I guess your provider block imgur.

  • mans_xdmans_xd Member

    @yokowasis said:

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @yokowasis said:

    @hennaboy said:

    @NotFoundException said:

    @NDTN said:
    The 30% policy is in place to stop resource abuse and prevent users from maxing out the CPU at 100% for hours on end on shared plans. We have never suspended a VPS just for running a quick benchmark. You're fine to burst over 30% usage occasionally when you need to, it's just not meant to be run at that level constantly.

    Are you enforcing it strictly? For example when my CPU usage hovers around 50-60% 18 hours a day, will you suspend it or will you contact through a ticket first, trying to find a solution?

    I spoke to them recently about something like this and they said it would be an email notification and invitation to discuss.

    I thought that was more than reasonable.

    Correction, it would be an email + a shutdown

    Actually no but whatever pot you with to stir

    Actually Yes.

    Content not available

    But at a guess it sucks to suck.

    https://imgur.com/C0P5ZKQ

    I guess your provider block imgur.

    i guess he is in UK

    https://www.bbc.com/news/articles/c4gzxv5gy3qo

  • freelanceonlinefreelanceonline Member

    Good uptime; the speed isn't as fast as Ramnode, but it's still good. I'm waiting for a special anniversary date; I'd like to see more offers from Greencloud. I'm interested in renting another VPS.

  • VelocityTierVelocityTier Member

    @lowendclient said:I have a suggestion: allow users to cap CPU usage at qemu via ticket, to help prevent website suspension during high traffic periods (days).

    This is a solid idea, but having to open a support ticket just to manually toggle a hypervisor cap during a traffic spike is a massive pain for production websites. If you are just running websites, you shouldn’t have to micromanage your own kernel limits or worry about 24-hour resource graphs. This is exactly why a cloud hosting environment built on CloudLinux and CageFS makes more sense for web traffic than a budget unmanaged VPS. Instead of guessing how a provider handles %user vs %iowait, or risking an abrupt suspension when a script flags your node, a proper cloud platform handles resource spikes gracefully. If your site suddenly runs a heavy backup or gets a massive wave of traffic, the system naturally queues the processes at the kernel level. Your site stays online, and the rest of the server neighbors stay completely unaffected—no tickets or manual QEMU capping required.

    Thanked by 1lowendclient
Sign In or Register to comment.