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
Don't forget to visit LET on mobile while traveling.
Many posts but don't see @Hetzner_OL answered a simple "Yes" or "No" question "Has Hetzner disabled CPU steal time reporting?" but I guess we can all make our assumptions by now.
Could I ask what difference a yes/no answer would make in this context? Just curious... --Katie
No difference. I just wanted to know.
I must use ChatGPT to understand this answer 🤣
If you have noticed performance issues that you think are on our end or are due to noisy neighbors, please write us a support request via your account Cloud Console. Our support team can then take a closer look at your specific situation. --Katie
I really prefer to disconnect while I am home with family in the states since I rarely see them. But I will check in when I am back. --Katie
So many words instead of yes or no, lol.
I am just going to assume it as a yes cpu steal reporting has been disabled since you refuse to answer the question.
I track steal on all my servers, and while some providers manage extremely low levels of steal, even VDS servers with dedicated CPU resources that have consistent performance report very small amounts of steal.
The fact that not a single one of my Hetzner cloud servers has ever reported any steal confirms that they do in fact hide the steal time from their customers.
The answer is: "Yes, but there's no performance loss anyway since we use another system to balance the nodes based on usage, so it would only report wrongly." Learn to read between the lines.
-2.000.000 social credit, your Hetzner account (alongside with you) will now be terminated.
..
Are you just guessing? They did not say any of what you wrote.
Why? Do I have to play puzzles and mind games with my simple support questions?
Bump!
So, @Hetzner_OL you disabled CPU steal reporting?
If you have noticed performance issues that you think are on Hetzner’s end or are due to noisy neighbors, please write Hetzner a support request via your account Cloud Console. Hetzner’s support team can then take a closer look at your specific situation. --Emgh
CPU steal reporting was never enabled. It was already officially confirmed in the Hetzner Forum.
It’s a question that has perplexed philosophers, baffled scientists, and left countless IT professionals scratching their heads in bewilderment. You see, the very essence of this inquiry delves deep into the labyrinthine corridors of server management, where the flickering lights of data centers cast long shadows over the intricate dance of ones and zeros.
Now, let us embark on a whimsical journey through the annals of hosting history. Picture, if you will, a time when servers roamed the digital plains like majestic beasts, each one equipped with a plethora of features, much like a Swiss Army knife of the virtual realm. Among these features, the noble CPU stealing reporting stands tall, a vigilant guardian of resource allocation, ensuring that no rogue process runs amok, pilfering precious CPU cycles like a raccoon rummaging through a trash can at midnight.
But alas, as with all good things, there comes a time when the winds of change blow through the data centers, and decisions must be made. Imagine a boardroom filled with hosting executives, each one donning a suit that could rival the finest tailors of Savile Row. They sit around a polished mahogany table, sipping artisanal coffee brewed from beans harvested under a full moon, discussing the merits and demerits of various features. “Shall we disable the CPU stealing reporting?” one might ponder, tapping a pen against their chin in deep contemplation. “But what of the customers?” another might counter, waving their hands dramatically as if conducting an orchestra of uncertainty.
And so, the debate rages on, echoing through the hallowed halls of the hosting company. Meanwhile, customers, blissfully unaware of the existential crisis unfolding behind the scenes, continue to navigate their digital landscapes, blissfully clicking away, unaware that their beloved CPU stealing reporting may be hanging in the balance like a piñata at a birthday party, waiting for the fateful swing of a bat.
As the clock ticks on, one can only wonder: has the CPU stealing reporting been disabled? Is it merely a figment of our collective imagination, a ghost in the machine, haunting the servers with whispers of what once was? Or perhaps it’s a strategic maneuver, a calculated decision made in the name of progress, efficiency, or perhaps even a secret plot to usher in a new era of hosting that we mere mortals cannot yet comprehend.
In conclusion, dear inquirer, while I cannot provide you with a definitive answer regarding the status of that elusive CPU stealing reporting, I can assure you that the world of hosting is as complex and multifaceted as a Rubik's Cube spun by a caffeinated octopus. So, whether the reporting is disabled or merely taking a sabbatical, let us raise a toast to the enigmatic nature of server management and the delightful absurdity of it all!
I hope this answered your question.
-- Wadhah, Senior Gaslighting Engineer.
You, Sir, are a legend!
I asked ChatGPT to summarize it, and it crashed.
GJ @wadhah
Ad you need to register to see that post? This is no. 1 bullshit
Basically the shared CPU plans are throttled with a 24h budget.
CX (Intel) = 20% per vCPU
CAX (ARM) = 30% per vCPU
CPX (AMD) = 33.3% per vCPU
If you utilize 100% of your CPU with shared plans it will be throttled to 33.3% with the AMD plans. That means if you have a plan with 4 cores for example you only can utilize 1.3 cores 24/7. You can see that within the Hetzner UI graphs, it will be stuck at 100-133%. Additionally steal is disabled so you don't see noisy neighbors and you can't be 100% sure if you are getting throttled because of high cpu usage by yourself or if you are on a bad node.
So, not 80%?