Most fast-takeoff AGI scenarios usually involve a singular intelligence created from an algorithm that easily scales based on how much computing power is allocated to it.<p>Combined with the notion of computing overhang[0], it&#x27;s possible that our very first AGI could far exceed human intelligence, such that it would have capacity for rapid self-improvement right from the start.<p>I&#x27;m not saying this will necessarily be the case; slower takeoff scenarios are certainly a possibility, albeit an unlikely one (IMHO).<p>Another point to consider is that computing hardware is vastly superior to the human brain both in its capacity for raw calculation, and its sheer speed in terms of raw latency.<p>Keeping that in mind, assume we have created an AGI simulation that&#x27;s approximately equal in complexity relative to the human brain. Not intelligence, just complexity of the simulation itself.<p>Now consider that AGI is not bound by biological constraints, and would not necessarily be structured in similar fashion to the human brain. This lends itself to potentially far more efficient architectures, and with that, the realization of AGI at a computational cost far below that of simulating a complete human brain.<p>Moreover, given a completely alien architecture, it&#x27;s not hard to imagine the cognitive side of such a simulation interfacing rather directly with traditional modes of computation.<p>To illustrate, imagine comparing a human being to an identical human being that has a microprocessor integrated into their brain. Both humans may have nearly identical capacity for abstract intelligence, but the one with the microprocessor is going to be effectively far more intelligent, simply because their capacity for dealing with raw data and calculations is vastly superior. It&#x27;s not hard to imagine a similar dynamic coming into play with AGI.<p>[0] <a href="http:&#x2F;&#x2F;wiki.lesswrong.com&#x2F;wiki&#x2F;Computing_overhang" rel="nofollow">http:&#x2F;&#x2F;wiki.lesswrong.com&#x2F;wiki&#x2F;Computing_overhang</a>