For infra systems, this is great: code against the GCS API, and let the user choose the cost/latency/durability tradeoffs that make sense for their use case.
Colossus for Rapid Storage
81–90 of 129 posts
Re: Colossus for Rapid Storage
#82If you want object storage faster than S3 Express One Zone or GCP Rapid Storage without the zonal limitation check out ACS: https://acceleratedcloudstorage.com You can bring data in and out of the GPU quickly and improve utilization.
Re: Colossus for Rapid Storage
#83(I work on Google storage)
Re: Colossus for Rapid Storage
#84Earlier quoted context omitted.
Hi, I'm looking for a job. Are you willing to pay me serious money to set up CFS as a service on your AWS?
Obviously not, since you could not deliver it. It seems that you maybe don't realize what CFS is in this context, and are thinking of something else that you could just "set up"? What jeffbee is talking about is Google's proprietary Colossus File System, and all its transitive dependencies.
It looks like every other clustered file system. What's special about Google's Colossus?
Re: Colossus for Rapid Storage
#85Earlier quoted context omitted.
Fair, how about instead of S3 Express they call it S3 Max (One Zone). It doesn’t take a rocket scientist to come up with good product names, just copy Apple. Though I suppose what happens when engineers are left up to the marketing. :-)
If Apple's so great at naming things, tell me (without looking) which is bigger/better/faster for their CPUs: Max or Ultra?
Re: Colossus for Rapid Storage
#86Earlier quoted context omitted.
Struggling to find a definition, but seemingly zonal just means there's a massive instance per cluster. Did find some interesting recent (March 28th, 2025) reads though! Colossus under the hood: How we deliver SSD performance at HDD prices https://cloud.google.com/blog/products/storage-data-transfer... I kind of thought you meant ZNS / https://zonedstorage.io/ at first, or it's more recent better awesomer counterpart…
In Google Cloud parlance, "regional" usually means "transparently master-master replicated across the availability zones within a region", while "zonal" means "not replicated, it just is where it is."
NB: I am on the rapid storage team.
Re: Colossus for Rapid Storage
#87Earlier quoted context omitted.
That link doesn't work for me, so here's the relevant bit: Rapid Storage: A new Cloud Storage zonal bucket that enables you to colocate your primary storage with your TPUs or GPUs for optimal utilization. It provides up to 20x faster random-read data loading than a Cloud Storage regional bucket. (Normally we wouldn't allow a post like this which cherry-picks one bit of a larger article, but judging by the community r…
There's now another blog post about Rapid storage specifically: https://cloud.google.com/blog/products/storage-data-transfer... . (That wasn't up yet when the original post was made.)
Re: Colossus for Rapid Storage
#88Earlier quoted context omitted.
That link doesn't work for me, so here's the relevant bit: Rapid Storage: A new Cloud Storage zonal bucket that enables you to colocate your primary storage with your TPUs or GPUs for optimal utilization. It provides up to 20x faster random-read data loading than a Cloud Storage regional bucket. (Normally we wouldn't allow a post like this which cherry-picks one bit of a larger article, but judging by the community r…
Apologies! First time making a post on hacker news, and I thought this was really exciting news. FWIW, I talked to the presenter after this was revealed during the NEXT conference today, and he seems to have implied that zonal storage is quite close to what Google seems to have with Colossus.
(I was just adding some explanation for more seasoned users who might wonder why we were treating this a bit differently.)
Also, welcome to posting on HN and we hope you'll continue!
Re: Colossus for Rapid Storage
#89Very cool! This makes Google the only major cloud that has low-latency single-zone object storage, standard regional object storage, and transparently-replicated dual-region object storage - all with the same API. For infra systems, this is great: code against the GCS API, and let the user choose the cost/latency/durability tradeoffs that make sense for their use case.
s3: https://aws.amazon.com/pm/serv-s3
s3 express: https://aws.amazon.com/s3/storage-classes/express-one-zone/
cross-region replication: https://docs.aws.amazon.com/AmazonS3/latest/userguide/replic...
Re: Colossus for Rapid Storage
#90There's a detailed blog post about Rapid Storage now available, see https://news.ycombinator.com/item?id=43645309 (I work on Google storage)