Read The Computers of Star Trek for Free Online

2.2 , the main computer system of the Enterprise consists of:
    (10 levels) * (4 processing modules per level) = 40 processing modules per main processing core
    That’s not even close to the 9,200 processors in the 1997 Intel supercomputer. But as we’ll see, each Trek processing module contains hundreds of thousands of nanoprocessors.

    FIGURE 2.2 Main Computer System

    Further, we’re told that each of the three main processing cores is redundant—that is, they run in “parallel clock-sync with each other, providing 100% redundancy.” And that they do this at rates “significantly higher than the speed of light.” What could this statement possibly mean? It’s one thing to say that data is transmitted at lightspeed. But it makes no sense to say that clock cycles per instruction run at lightspeed or that the clock cycle time is significantly higher than lightspeed. This is the same as claiming that a clock runs at 900,000 kilometers per second. Clocks don’t run in kilometers, millimeters, or any other spatial unit. Machine speed is measured in operations per second, not in kilometers per second.
    On the other hand, we can make the very vague statement that the faster a signal travels during a finite amount of time, the more operations the machine processes per second. If each signal represents one operation, and signals suddenly travel more quickly, then okay, the computer might process more instructions per time unit. But remember that Moore’s Law (in one of its versions) says that computer speed doubles every 18 months. If we took an optical computer (where signals travel, say, at lightspeed) and replaced all its circuitry with FTL circuitry (where signals travel three times as fast), we might triple our computer’s processing speed. Under Moore’s Law, that’s a gain of just over two years.
    And having signals travel 900,000 kilometers per second adds very little speed if the circuit is microscopic. And wouldn’t the system clock run backwards? Wouldn’t information arrive before it was sent?—and so get sent back again in an endless sequence?
    And...
    As McCoy might say, “Damn it, Jim, we’re computer scientists, not physicists!”
    Let’s continue our journey through the Technical Manual . The manual states that if one of the main processing cores in the primary hull fails, then the other assumes the total primary computing
load for the ship without interruption. Also that the main processing core in the engineering hull is a backup, in case the two primary units fail. So ... why do the holodeck simulations get interrupted in so many episodes? Why do the food replicators constantly go haywire? In The Next Generation episode “Cost of Living,” two hundred replicators break down. e Are all three main processing cores down? If so, how is anything running?
    Perhaps if we look more closely at the main processing core itself ( Figure 2.3 ), as described in the manual, we’ll come up with an answer.
    Each main processing core is made up of a series of miniature subspace field generators (MSFG). These create a symmetrical (nonpropulsive) field distortion of 3350 millicochranes within the FTL core elements. According to the manual, “This permits transmission and processing of optical data within the core at rates significantly higher than lightspeed.” 3
    Further, we’re told that a nanocochrane is a measure of subspace field stress and is equal to one billionth of a cochrane. These definitions are about warp speed. A cochrane is the amount of field stress needed to generate a speed of c, the speed of light. One cochrane = c, 2 cochranes = 2c, and so on.
    Warp factor 1 = 1 cochrane
    Warp factor 2 = 10 cochranes
    Warp factor 3 = 39 cochranes

    FIGURE 2.3 Main Processing Core

    There’s even a chart in the Technical Manual that shows “velocity in multiples of lightspeed” on the y-axis and “warp