@HiddenLayer555@lemmy.ml to Memes@lemmy.mlEnglish • 6 days agoIs 8GB a lot? Depends on the context.lemmy.mlimagemessage-square46fedilinkarrow-up1267arrow-down10
arrow-up1267arrow-down1imageIs 8GB a lot? Depends on the context.lemmy.ml@HiddenLayer555@lemmy.ml to Memes@lemmy.mlEnglish • 6 days agomessage-square46fedilink
minus-squareRob299 - she/herlinkfedilinkEnglish19•6 days ago1 tb is a good start for most use case. 5 tb…? now you’re getting somewhere.
minus-square@ferric_carcinization@lemmy.mllinkfedilinkEnglish4•6 days agoYou’re talking about register width, right?
minus-square@ferric_carcinization@lemmy.mllinkfedilinkEnglish3•4 days agoBut something could easily go wrong with such large registers & access would be slow. Maybe we should have RAID 1 for registers?
minus-square@Opisek@lemmy.worldlinkfedilink3•edit-24 days agoI only ever opt for RAID 5. It also help to use error correcting hardware.
minus-square@ferric_carcinization@lemmy.mllinkfedilinkEnglish3•4 days agoFor such large registers, I think error correction for the error correction might be useful.
1 tb is a good start for most use case. 5 tb…? now you’re getting somewhere.
L1 cache?
Registers
You’re talking about register width, right?
Yeah, 5TB for every register of course.
But something could easily go wrong with such large registers & access would be slow. Maybe we should have RAID 1 for registers?
I only ever opt for RAID 5. It also help to use error correcting hardware.
ECC cache
For such large registers, I think error correction for the error correction might be useful.