HiddenLayer555@lemmy.ml to Memes@lemmy.mlEnglish · 2 days agoIs 8GB a lot? Depends on the context.lemmy.mlimagemessage-square48fedilinkarrow-up1245arrow-down16
arrow-up1239arrow-down1imageIs 8GB a lot? Depends on the context.lemmy.mlHiddenLayer555@lemmy.ml to Memes@lemmy.mlEnglish · 2 days agomessage-square48fedilink
minus-squareRob299 - she/her@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up19·2 days ago1 tb is a good start for most use case. 5 tb…? now you’re getting somewhere.
minus-squareferric_carcinization@lemmy.mllinkfedilinkEnglisharrow-up4·1 day agoYou’re talking about register width, right?
minus-squareOpisek@lemmy.worldlinkfedilinkarrow-up4·7 hours agoYeah, 5TB for every register of course.
minus-squareferric_carcinization@lemmy.mllinkfedilinkEnglisharrow-up2·2 hours agoBut something could easily go wrong with such large registers & access would be slow. Maybe we should have RAID 1 for registers?
minus-squareOpisek@lemmy.worldlinkfedilinkarrow-up3·edit-21 hour agoI only ever opt for RAID 5. It also help to use error correcting hardware.
minus-squareferric_carcinization@lemmy.mllinkfedilinkEnglisharrow-up1·9 minutes 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.