Replication backpack: Difference between revisions
Jump to navigation
Jump to search
basic page |
m added commas |
||
| Line 3: | Line 3: | ||
Or '''replication backpack overhead'''. | Or '''replication backpack overhead'''. | ||
The more monolithic compact self contained and complete a self replication process ought to be <br> | The more monolithic, compact, self contained, and complete a self replication process ought to be <br> | ||
the more stuff needs to be replicated and possibly even lugged around (thus replication '''backpack'''). | the more stuff needs to be replicated and possibly even lugged around (thus replication '''backpack'''). | ||
Latest revision as of 12:39, 25 April 2025
Or replication backpack overhead.
The more monolithic, compact, self contained, and complete a self replication process ought to be
the more stuff needs to be replicated and possibly even lugged around (thus replication backpack).
- Replicating the code for replication in hardware storage (like cells in DNA) usually not considered for technical systems.
- Replication data IO channels rather than saving by sharing them over bigger subsystems
- Replicating higher assembly levels stages for each system making them heavily underrutilized rather than sharing
- restricted balancing with power units
- and many more
More distributed systems can avert these issues: See:
Related
- Why ultra-compact molecular assemblers are too difficult
- Molecular assemblers as advanced productive nanosystem (outdated)