HNHacker News
TopNewBestAskShowJobs

g413n

84 karma · joined November 4, 2024

submissionscomments
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
yeah we're very interested in trying toploaders, we'll do a test rack next time we expand and switch to that if it goes well.

w.r.t. testing the main thing we did was try to buy a bit from each supplier a month or two ahead of time, so by the time we were doing the full build that rack was a known variable. We did find one drive lot which was super sketchy and just didn't include it in the bulk orders later. diversity in suppliers helps a lot with tail risk

g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
yeah colo help has been great, we had a power blip and without any hassle they covered the cost and installation of UPSes for every rack, without us needing to think abt it outside of some email coordination.
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
not caring about redundancy/reliability is really nice, each healthy HDD is just the same +20TB of pretraining data and every drive lost is the same marginal cost.
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
fwiw our first test rack has been up for about a year now and the full cluster has been operational for training for the past ~6 months. having it right down the block from our office has been incredibly helpful, I am a bit worried abt what e.g. freemont would look like if we expand there.

I think another big crux here is that there isn't really any notion of cluster-wide downtime, aside from e.g. a full datacenter power outage (which we've had ig, and now have UPSes in each rack kindly provided and installed by our datacenter). On the software/network level the storage isn't really coordinated in any manner, so failures of one machine only reflect as a degradation to the total theoretical bandwidth for training. This means that there's generally no scrambling and we can just schedule maintenance at our leisure. Last time I drew straws for maintenance I clocked a 30min round-trip to walk over and plug a crash cart into each of the 3 problematic machines to reboot and re-intialize and that was it.

Again having it right by the office is super nice, we'll need to really trust our kvm setup before considering anything offsite.

g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
yeah we just have the 100gig link, atm that's about all the gpu clusters can pull but we'll prob expand bandwidth and storage as we scale.

I guess worth noting that we do have a bunch of 4090s in the colo and it's been super helpful for e.g. calculating embeddings and such for data splits.

g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
someone has to go and power-cycle the machines every couple months it's chill, that's the point of not using ceph
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
the doodles are great
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
in a datacenter context failure rates are just a remote-hands recurring cost so it's not too bad with front-loaders

e.g. have someone show up to the datacenter with a grocery list of slot indices and a cart of fresh drives every few months.

g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
7.5k for zayo 100gig so that's like half of the MRC
g413n··on Building the heap: racking 30 petabytes of hard drives for pretraining
No mention of disk failure rates? curious how it's holding up after a few months
← PreviousPage 2 of 2