←back to thread

261 points tosh | 1 comments | | HN request time: 0s | 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 #
blibble ◴[] No.42069210[source]
I just cat'ed /proc/cpuinfo on my Hetzner and AWS machines

AWS: E5-2680 v4 (2016)

Hetzner: Ryzen 5 (2019)

replies(1): >>42071461 #
dilyevsky ◴[] No.42071461{3}[source]
Now do hard drives
replies(2): >>42072132 #>>42072929 #
1. blibble ◴[] No.42072132{4}[source]
the hetzner one is a dedicated pcie 4.0 nvme device and wrote at 2.3GB/s (O_DIRECT)

the AWS one is some emulated block device, no idea what it is, other than it's 20x slower