←back to thread

257 points tosh | 2 comments | | HN request time: 0.001s | source
Show context
turtlebits ◴[] No.42068395[source]
Is this really an AWS issue? Sounds like you were just burning CPU cycles, which is not AWS related. WebSockets makes it sound like it was a data transfer or API gateway cost.
replies(2): >>42068522 #>>42068890 #
VWWHFSfQ ◴[] No.42068522[source]
> Is this really an AWS issue?

I doubt they would have even noticed this outrageous cost if they were running on bare-metal Xeons or Ryzen colo'd servers. You can rent real 44-core Xeon servers for like, $250/month.

So yes, it's an AWS issue.

replies(1): >>42068676 #
JackSlateur ◴[] No.42068676[source]

  You can rent real 44-core Xeon servers for like, $250/month.
Where, for instance ?
replies(3): >>42068729 #>>42068739 #>>42068788 #
Faaak ◴[] No.42068729[source]
Hetzner for example. An EPYC 48c (96t) goes for 230 euros
replies(1): >>42068782 #
dilyevsky ◴[] No.42068782[source]
Hetzner network is complete dog. They also sell you machines that are long should be EOL’ed. No serious business should be using them
replies(3): >>42068965 #>>42069178 #>>42069210 #
dijit ◴[] No.42068965[source]
What cpu do you think your workload is using on AWS?

GCP exposes their cpu models, and they have some Haswell and Broadwell lithographies in service.

Thats a 10+ year old part, for those paying attention.

replies(2): >>42069283 #>>42069684 #
tsimionescu ◴[] No.42069684{5}[source]
I think they meant that Hetzner is offering specific machines they know to be faulty and should have EOLd to customers, not that they use deprecated CPUs.
replies(1): >>42069729 #
1. dijit ◴[] No.42069729{6}[source]
Thats scary if true, any sources? My google-fu is failing me. :/
replies(1): >>42070304 #
2. akvadrako ◴[] No.42070304[source]
It's not scary, it's part of the value proposition.

I used to work for a company that rented lots of hetzner boxes. Consumer grade hardware with frequent disk failures was just what we excepted for saving a buck.