Here's the original article linked at the bottom: https://www.theregister.com/2023/01/02/nonbinary_ddr5_is_finally_coming/ I found OP's link was pretty short on details regarding what "Non-binary...
"Non-binary" means "units with capacities which are not a power of two bits" (e.g. 24GB, rather than 16GB or 32GB). Personally, I do not think this will be a game-changer for businesses...
"Non-binary" means "units with capacities which are not a power of two bits" (e.g. 24GB, rather than 16GB or 32GB).
Personally, I do not think this will be a game-changer for businesses everywhere. If for some reason the cost of the next binary step is prohibitive, by definition these are modules—just socket mismatched modules in your system. If the loss of dual-channel matters performance-wise, then probably your budget should allow for a bit of memory headroom. It's not useless, certainly; but "game-changing" seem very unlikely to me.
is it bad if, despite my past graduate computer architecture work, I just want to pretend that non-binary memory bucks binary memory expectations by defining it's own memory roles for itself? And...
is it bad if, despite my past graduate computer architecture work, I just want to pretend that non-binary memory bucks binary memory expectations by defining it's own memory roles for itself? And defies boundaries and imagines new futures and helps the comp arch community acknowledge just how trans computing is? Instead of, ya know, being 24GB?
Here's the original article linked at the bottom:
https://www.theregister.com/2023/01/02/nonbinary_ddr5_is_finally_coming/
I found OP's link was pretty short on details regarding what "Non-binary RAM" actually is. Just that it's new and highly anticipated.
"Non-binary" means "units with capacities which are not a power of two bits" (e.g. 24GB, rather than 16GB or 32GB).
Personally, I do not think this will be a game-changer for businesses everywhere. If for some reason the cost of the next binary step is prohibitive, by definition these are modules—just socket mismatched modules in your system. If the loss of dual-channel matters performance-wise, then probably your budget should allow for a bit of memory headroom. It's not useless, certainly; but "game-changing" seem very unlikely to me.
is it bad if, despite my past graduate computer architecture work, I just want to pretend that non-binary memory bucks binary memory expectations by defining it's own memory roles for itself? And defies boundaries and imagines new futures and helps the comp arch community acknowledge just how trans computing is? Instead of, ya know, being 24GB?
It might matter a lot to someone deploying 10s of thousands of servers with specific memory requirements.