Efficiency sounds so nice, but ever since working on a safety based project and observing
1) Efficiency hates redundancy
2) Redundancy is, like, the easiest, most zero-thought way of adding robustness
I've been a little suspicious of efficiency.
And we see questionable efficiency optimizations all over -- here in an individual business, in the greater economy (Let's over-specialize our economies, it is more efficient. Let's JIT manufacture everything, buffers cost warehouse space).
Just add redundancy. It'll be twice as expensive but it won't explode if something goes wrong.
If robustness is what's important to you, then your challenge is to do that efficiently.
For example, maybe you can use something like the Reed–Solomon error correction, which allows you to balance between no redundancy and full duplication, both in cost and benefit.
1) Efficiency hates redundancy
2) Redundancy is, like, the easiest, most zero-thought way of adding robustness
I've been a little suspicious of efficiency.
And we see questionable efficiency optimizations all over -- here in an individual business, in the greater economy (Let's over-specialize our economies, it is more efficient. Let's JIT manufacture everything, buffers cost warehouse space).
Just add redundancy. It'll be twice as expensive but it won't explode if something goes wrong.