Live data from Hacker News

Cash App migrated 400TB of data to PlanetScale's cloud

planetscale.com

1–10 of 15 posts

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#3

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#4

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

The article says,

> At peak times, Cash App's database handles approximately 3–4 million queries per second (QPS) across 400 shards, totaling around 400TiB of data.

400TiB represents not a lot of this data. If each query stored only 1 byte, this would only be 4 years worth of this data.

If duplicated, or processed and the results stored, that would add up, too.

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#5

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

It's peer-to-peer payments and banking, which have been around for much longer than the stocks/bitcoin aspect of the app.

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#6

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

It's not much data.

With current 22TB magnetic disks it's less than 20 disks, they would fit into a single machine (4u, likely).

The Storinator XL60 from 45drives (https://www.45drives.com/products/storinator-xl60-configurat...) can hold 60 disks, for (advertised) ~1.4PB of data.

(btw i've learned about 45drives through Linus Tech Tips channel so I think it's obligatory to say LTTSTORE.COM - for the meme)

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#7

Earlier quoted context omitted.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

The article says, > At peak times, Cash App's database handles approximately 3–4 million queries per second (QPS) across 400 shards, totaling around 400TiB of data. 400TiB represents not a lot of this data. If each query stored only 1 byte, this would only be 4 years worth of this data. If duplicated, or processed and the results stored, that would add up, too.

Why would a query store data? Are they logging individual queries?

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#8
post #6

Earlier quoted context omitted.

It would be interesting to know why a Bitcoin application requires 400 TB of disk space.

It's not much data. With current 22TB magnetic disks it's less than 20 disks, they would fit into a single machine (4u, likely). The Storinator XL60 from 45drives ( https://www.45drives.com/products/storinator-xl60-configurat... ) can hold 60 disks, for (advertised) ~1.4PB of data. (btw i've learned about 45drives through Linus Tech Tips channel so I think it's obligatory to say LTTSTORE.COM - for the meme)

45drives is... bad. I cannot understand why people would use them- particularly for homelab. Three SC846 24x3.5" 4U can be had for no more than $400/ea and, theres 36bay versions.

60 drives in 6U is a crap ton of weight.

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#9

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

The article says they used a forked version of Vitess with customizations. What were they and how did you address that when migrating?

Re: Cash App migrated 400TB of data to PlanetScale's cloud

#10
post #9

We've loved working with the incredible team at Cash App. If anyone has questions myself or someone on the PlanetScale team will answer.

The article says they used a forked version of Vitess with customizations. What were they and how did you address that when migrating?

Answering on behalf of PlanetScale (I'm the CTO!). I don't remember exactly what was different from upstream, but it wasn't a whole lot of changes.

Fortunately, PlanetScale runs a well-maintained fork ourselves, so we're very used to taking custom changes and getting them deployed. In this case, we asked the Block team for all of their changes and went through them one by one to see what was needed to pull into our fork.

By the time we did the migration, we made sure that any behavior wouldn't be different where it mattered.

Post reply on HN