Hemocoel Pipelines as a Microprocessor

We are tempted to consider the hemocoel as a microprocessor. Its unique parallel processing capability comes from the idea that the hemocoel 'pipelines' in that many steps of many parallel sequences operate concurrently. Designers increase a system's clock rate or speed by using scaling technology to make chips smaller and by reducing the numbers of levels of logic each cycle needs (more levels means longer time). However, using detailed wire and component models, many of today's designs scale poorly with technology (Ref: Agarwal et al., 2000). If each step has limited time to execute, the time the hemocoel saves by pipelining is proportional to how many stages are active. Low-level "instructions" given to the "hardware of the hemocoel" might include something about the dynamics of the hemolymph. The number of stages of processing a hemocoel completes each second as in a processor would be the hemocoel's "clock rate". For example, in comparison, a personal computer using a 200-megaherz clock might execute two hundred million stages each second. We have no idea of what a hemocoel's clock rate might be.

The hemocoel is uniquely organized to incorporate 'supra-scalar' tasks in which more than one set of instructions might be performed in separate places at each stage. Because the controlled units of biological systems are cells or tissues, we might imagine a cache of memory, perhaps analogous to extranuclear DNA, held and used at the site of the processor itself. The cache would hold only parts of a central genetic program that the system most frequently refers to, thereby avoiding having to call on more distant memory.

0 0

Post a comment