Live data from Hacker News

How AWS S3 serves 1 petabyte per second on top of slow HDDs

bigdata.2minutestreaming.com

101–110 of 172 posts

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#101

> tens of millions of disks If we assume enterprise HDDs in the double digit TB range then one can estimate that the total S3 storage volume of AWS is in the triple digit Exabyte range. That's propably the biggest storage system on planet earth.

Production scale enterprise HDDs are in the 30TB range, 50TB on the horizon...

Yes, WD 28-30TB range; we have a sku with 1000+ drives per rack and it weighs more than a ton.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#102

Earlier quoted context omitted.

It's assumed that the new S3 Express One Zone is backed by SSDs but I believe Amazon doesn't say so explicitly.

I've always felt it's probably a wrapper around the Amazon EFS due to the similar pricing and that S3 One Zone has "Directory" buckets, a very file system-y idea.

nope

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#103
post #52

Earlier quoted context omitted.

My own assumption was always that the cold tiers are managed by a tape robot , but managing offlined HDDs rather than actual tapes.

I think that's close to the truth. IIRC it's something like a massive cluster of machines that are effectively powered off 99% of the time with a careful sharding scheme where they're turned on and off in batches over a long period of time for periodic backup or restore of blobs.

it's amazing that Glacier is such a huge system with so many people working on it and it's still a public mystery how it works. I've not seen a single confirmation of how it works..

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#104
post #9

So is any of S3 powered by SSD's? I honestly figured that it must be powered by SSD for the standard tier and the slower tiers were the ones using HDD or slower systems.

Std has the same performance as every other storage class. There are 2 async classes which you can't read from without retrieving first, but that's not a 'performance' difference as such - GETs aren't slow, they fail.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#106

It is interesting that even after falling prices of HDDs, S3 costs have remained the same for at least 8 years. There's just not enough competition to push them to reduce costs. But imagine money it brings in in AWS because of this.

Same with every other aspect of their offerings. Look at EC2 even with instances like m7a.medium, 1 vCPU (not core) and 4GB memory for ~$50 USD/month on demand or ~$35/month reserve 1 year. It isn't even close to be competitive outside other big cloud providers.

EDIT: clarity on monthly pricing.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#107

It is interesting that even after falling prices of HDDs, S3 costs have remained the same for at least 8 years. There's just not enough competition to push them to reduce costs. But imagine money it brings in in AWS because of this.

There is inflation, so it has effectively dropped in price. But your point is taken: inflation’s effect on prices is most assuredly slower than the progress of technology’s effect.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#108

Earlier quoted context omitted.

I dunno, the article's tl;dr is just parallelism. Data gets split into redundant copies, and is rebalanced in response to hot spots. Everything in this article is the obvious answer you'd expect.

It's not really "redundant copies". It's erasure coding (ie, your data is the solution of an overdetermined system of equations).

That’s just fractional redundant copies.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#109

It is interesting that even after falling prices of HDDs, S3 costs have remained the same for at least 8 years. There's just not enough competition to push them to reduce costs. But imagine money it brings in in AWS because of this.

How much have hdd prices really fallen? AFAIK the incredible improvements in price per byte in HDD had slowed so much that they'll be eclipsed by SSDs in a few years.

Re: How AWS S3 serves 1 petabyte per second on top of slow HDDs

#110
post #11

Does anyone know what is the technology stack of S3? Monolith or multiple services? I assume would have lots of queues, caches and long running workers.

At this kind of scale, queues, caches and long running workers ought to be avoided at all costs due to their highly opaque nature which drastically increases the unpredictability in the system's behaviour whilst decreasing the reliability and observability.
Post reply on HN