I have 384TB of ECC DDR4 across two blades with 4 CPUs for a combined core count of 96.

@bob_zim @SecurityWriter

Well he only said "DDR4", not that it is used as the systems memory. And PCIe add-on cards for ramdisks exist, sooo

@SecurityWriter Blimey! The system requirements for running MS Office are just getting ridiculous aren't they?

Also, when the AI bubble bursts, the 32GB of ECC DRAM in my ancient Mac Pro will probably be worth more than the entire stock market.

@agowa338 @bob_zim @SecurityWriter which is pretty unlikely for a SAN - if he said 48 TB or something it would be possible but unless you have very very very specialized boards I dont think you get up to 96TB per socket on ddr4 in any cases I know about

@agowa338 @bob_zim @SecurityWriter that being said things like Solid State Sans do have some highly specialized hw setups so we might be totally off

@adrianww @SecurityWriter You mean just before? When it bursts it'll be worthless due to liquidation of AI companies flooding the market.

@adrianww @SecurityWriter You mean just before? When it bursts it'll be worthless due to liquidation of AI companies flooding the market.

@cursedsql @bob_zim @SecurityWriter

Hence why I asked

I have 384TB of ECC DDR4 across two blades with 4 CPUs for a combined core count of 96.

It powers a fully populated 192 disk solid state SAN.

I was told it was old and in need of replacing, but apparently now it’s worth more than the GDP of the UK.

Can’t afford to run it (or hear my thoughts when in the vicinity)… but I can sit atop it like a fucking dragon.

And I will.

@agowa338 @cursedsql @bob_zim @SecurityWriter
I also would lean towards it being GB, although 384 GB does seem quite modest for what I assume is quite a high performance SAN, given it's all solid state.
I once worked on a mid range combined NAS/SAN head that topped out at 1TB for the high-end model. That wasn't just connected to the CPUs, it was also in caches and buffers for other chips in the data path.
That was a few years ago, and I can imagine a high end system might have a lot more, but 384TB does sound excessive, especially if there's only 192 SSDs hanging off it. It might be possible to load the entire array into RAM in that case.

@GerardThornley @agowa338 @bob_zim @SecurityWriter yes that's why I figured it was still credible because anyone who has a 384 tb solid state san might be rich enough to back it entirely in ram

I have 384TB of ECC DDR4 across two blades with 4 CPUs for a combined core count of 96.

It powers a fully populated 192 disk solid state SAN.

I was told it was old and in need of replacing, but apparently now it’s worth more than the GDP of the UK.

Can’t afford to run it (or hear my thoughts when in the vicinity)… but I can sit atop it like a fucking dragon.

And I will.

@GerardThornley @agowa338 @bob_zim @SecurityWriter also if they were 8tb instead of 2tb it would just be like a huge working set

@bob_zim @SecurityWriter

Well he only said "DDR4", not that it is used as the systems memory. And PCIe add-on cards for ramdisks exist, sooo

@cursedsql @agowa338 @bob_zim @SecurityWriter I don't know what's typical for these things with solid state, but with spinning rust (and a few years ago) large arrays typically didn't use drives much bigger than about 600GB. The preference would be for more drives, rather than larger. The reason for that was to do with failure rates, rebuild times and bandwidth.
The maths might have changed with the technology, but I'd suggest that if you're using SSDs then your focus is probably response time and bandwidth rather than storage density, so I'd expect smaller rather than larger drives.

@GerardThornley @cursedsql @bob_zim @SecurityWriter

Or you want to place it in an environment where it has to deal with heavy vibrations. Like on a moving trolly or in a vehicle or ... there are multiple reasons for this. It may even just be because you need high random IO speeds...

And the sizing also depends on what you're using it for. Like e.g. if you get your data in to the system in infrequent busts but at multiple TB/s and you've to cache it until it is synced even to SSDs, well

@agowa338 Cards like that exist, but they don’t hold thousands of DIMMs.

@GerardThornley @cursedsql @bob_zim @SecurityWriter

Or you want to place it in an environment where it has to deal with heavy vibrations. Like on a moving trolly or in a vehicle or ... there are multiple reasons for this. It may even just be because you need high random IO speeds...

And the sizing also depends on what you're using it for. Like e.g. if you get your data in to the system in infrequent busts but at multiple TB/s and you've to cache it until it is synced even to SSDs, well

@GerardThornley @cursedsql @bob_zim @SecurityWriter

(The later was an example from scientific environments. I think it was CERN but I'm not sure...)