# Everything you know about complexity is wrong

Who would disagree that the run-time of mergesort is and it’s asymptotically optimal? Not many programmers I reckon, except perhaps to question whether it’s talking about a model of computation that’s not sufficiently close to a real computer, for example a quantum computer or one that performs arbitrary operations in parallel (possibly involving sticks of spaghetti).

However, if you try to understand how to formalize what it means for a sort to run in and for it to be optimal, it’s surprisingly difficult to find a suitable computational model, that is, an abstraction of a computer which elides all but the important details of the computer: the operations it can perform, and how the memory works.

In this post, I’ll look at some of the most common computational models used in both practice and theory, and find out that they’re all flawed in one way or another, and in fact in all of them either mergesort doesn’t run in or there’s asymptotically faster sorts.

## Model 1: RAM is fixed-sized words

First up is a pragmatic model. Here, every item is assumed to fit into a 64-bit word of RAM.

This has an immediate problem: in a model where every item must fit into a 64-bit word, there’s only unique items, so an array of items can contain at most unique items. This makes sorting possible in time using a bucket sort with buckets.

Another, more subtle, problem here is that the registers of our machine must also be 64-bit. That means that there’s a finite (albeit huge) range of memory available to programs, which means that we can’t even represent large arrays.

This model isn’t abstract enough, and the constraint that everything fits in a single word is too restrictive. Since what we’d do in practice is to span large data across multiple words, let’s consider a model that’s like that.

## Model 2: Data spans multiple fixed-sized words.

Here, we allow data to be stored across multiple fixed-sized words, just like a real computer. In this model, to have an array of items, we’ll need each item to have bits. If we try to use fewer bits, we’ll have too many of them the same, and like in the first model, we’ll be able to sort in linear time.

Now, when we try mergesort we get that each comparison takes time, which means that even if every other detail works out, we’re going to have at best an run-time.

Again like the fixed-sized word model, we have the additional subtlety about how registers work. They need to be able to store arbitrarily large integers, and it’s not obvious how to design the machine so that adding to a register is (which is necessary for random access into an array), whilst avoiding adding a computational backdoor that allows programs to use registers instead of RAM, giving our machine the power of the next couple of models.

## Model 3: RAM is variable-sized words.

This model (a common one in the study of algorithmic complexity, and is also called the transdichotomous model) models memory as words each of bits. However, unlike the “RAM is fixed sized words” model, this depends on the size of the input to a problem, and in fact for a problem of size , .

This model starts well: merge sort runs in time. Unfortunately though, it can be exploited to do an unreasonable amount of computation with the wide memory locations. A paper by Fredman, “Surpassing the information-theoretic bound with fusion trees” (1993), shows that in this model there exists time sorts, using the idea of a Fusion Tree.

## Model 4: RAM is arbitrary integers.

This model allows each memory cell to contain an arbirarily large integer. It’s already obvious that this model isn’t going to satisfy us since it’s strictly more powerful than model 3. However, even though this model has diverged from what we think of as a computer, it’s surprising how powerful this model is.

A paper by Arnold Schönhage “On the power of random access machines” (2005) shows that in this model, any PSPACE problem can be solved in polynomial time. Since PSPACE includes all of NP, this is quite a feat. While in no way comparable to the paper, a hint to how to use arbitrary integer arithmetic to perform parallel computation is my blog post on computing Fibonacci numbers.

We could try to adjust the costs of arithmetic to be proportional to the number of bits used (called the “bit cost” model). That fixes the PSPACE P problem, but like the “data spans multiple words” model, we can’t use merge-sort to sort things in time.

## Conclusion

Every one of our models we’ve looked at has either failed to allow merge sort to work in , or has enabled faster algorithms. That’s not a proof that there’s no good model, but it’s certainly suggestive.

Even though the gap between complexity theory and its application to programming is wider than it looks, it’d be silly to write off complexity theory as useless. In practice it works well and has good predictive power, perhaps because the calculations that we do to compute complexity approximate a more bounded notion, where “this algorithm is ” means “until gets unreasonably large, and maybe excluding a handful of small edge-cases, the run-time is approximately some smallish constant times .” Because that’s much more like what we care about.