ENGINEERING ★ 82 upvotes 2012

Hetzner mail to customers: 1 megawatt more power due to leap second

The Founder's Submission

Direct narrative and submission text authored by @Uchikoma on Hacker News:

(Was Google translate, now from the comment of imaginator below, thanks)

Better translation of their message to English speaking customers:

During the night of 30.06.2012 to 01.07.2012 our internal monitoring systems registered an increase in the level of IT power usage by approximately one megawatt.

The reason for this huge surge is the additional switched leap second which can lead to permanent CPU load on Linux servers.

According to heise.de, various Linux distributions are affected by this. Further information can be found at: http://www.h-online.com/open/news/item/Leap-second-Linux-can...

In order to reduce CPU load to a normal level again, a restart of the whole system is necessary in many cases. First, a soft reboot via the command line should be attempted. Failing that, you have the option of performing a hardware reset via the Robot administration interface. For this, select menu item "Server" and the "Reset" tab for the respective server in the administration interface. Please do not hesitate to contact us, should you have any queries.

Kind regards,

Hetzner Online AG Stuttgarter Str. 1 91710 Gunzenhausen / Germany info@hetzner.de http://www.hetzner.com

Retrospective Overview & Key Insights

Distilled analysis of the business dynamics, operational challenges, and strategic takeaways:

In this technical retrospective (2012), @Uchikoma shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.

Core Principles for Independent Builders:
1
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
2
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
3
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:

HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.

Community Discussions & Critical Reviews

High-signal perspectives, counter-arguments, and peer founder insights debated on Hacker News (26 total discussions):

IM @imaginator Peer Contributor
ST @StavrosK Peer Contributor
ET @etaty Peer Contributor

OVH https://twitter.com/olesovhcom/status/220142781895671810

IM @imaginator Peer Contributor

Nice graph from Hetzner showing the spike:

http://imgur.com/a/ykoup

EF @efutch Peer Contributor

Perhaps nitpicking, but this is because of a bug in the leap second implementation, not in the leap second per se.

HISTORICAL ERA Web 2.0 Genesis (2007–2013)
COMMUNITY SCORE ★ 82 points
TOTAL DISCUSSIONS 26 comments
TOPICS & TECH STACK: