Editing Asymptotic analysis

In theoretical computer science, '''asymptotic analysis''' is the most frequently used technique to quantify the performance of an [[algorithm]]. Its name refers to the fact that this form of analysis neglects the exact amount of time or memory that the algorithm uses on specific cases, but is concerned only with the algorithm's asymptotic behaviour&mdash;that is, how the algorithm performs in the limit of infinite problem size.

==Irrelevance of constant factor==
It does this by neglecting the so-called [[invisible constant factor]]. The reasoning is as follows. Suppose Alice and Bob each write a program to solve the same task. Whenever Alice's program and Bob's program are executed with the same input on a given machine (which we'll call ALOPEX), Alice's program is always about 25% faster than Bob's program. The table below shows the number of lines of input in the first column, the execution time of Alice's program in the second, and the execution time of Bob's program in the third:
{|
! N
! Alice
! Bob
|-
| 10<sup>4</sup>
| 0.026
| 0.032
|-
| 10<sup>5</sup>
| 0.36
| 0.45
|-
| 10<sup>6</sup>
| 3.8
| 4.7
|}
Practically speaking, Alice's program is faster. In theory, however, the two programs have equally efficient algorithms. This is because an algorithm is an abstraction independent of the machine on which it runs, and we could make Bob's program just as fast as Alice's by running it on a computer that is 25% faster than the original one.

If this argument sounds unconvincing, consider the following argument. Programs, as they run on real machines, are built up from a series of very simple instructions, each of which is executed in a period of time on the order of a nanosecond on a typical microcomputer. However, some instructions happen to be faster than others.

Now, suppose we have the following information:
* On ALOPEX, the <code>MULTIPLY</code> instruction takes 1 nanosecond to run whereas the <code>DIVIDE</code> instruction takes 2 nanoseconds to run.
* We have another machine, which we'll call KITSUNE, on which these two instructions both take 1.5 nanoseconds to run.
* When Bob's program is given 150000 lines of input, it uses 1.0&times;10<sup>8</sup> multiplications and 3.0&times;10<sup>8</sup> divisions, whereas Alice's program uses 4.0&times;10<sup>8</sup> multiplications and 0.8&times;10<sup>8</sup> divisions on the same input.
Then we see that:
# On ALOPEX, Bob's program will require (1&nbsp;ns)&times;(1.0&times;10<sup>8</sup>) + (2&nbsp;ns)&times;(3.0&times;10<sup>8</sup>) = 0.70&nbsp;s to complete all these instructions, whereas Alice's program will require (1&nbsp;ns)&times;(4.0&times;10<sup>8</sup>) + (2&nbsp;ns)&times;(0.8&times;10<sup>8</sup>) = 0.56&nbsp;s; Alice's program is faster by 25%.
# On KITSUNE, Bob's program will require (1.5&nbsp;ns)&times;(1.0&times;10<sup>8</sup>) + (1.5&nbsp;ns)&times;(3.0&times;10<sup>8</sup>) = 0.60&nbsp;s, whereas Alice's will require (1.5&nbsp;ns)&times;(4.0&times;10<sup>8</sup>) + (1.5&nbsp;ns)&times;(0.8&times;10<sup>8</sup>) = 0.72&nbsp;s. Now Bob's program is 20% faster than Alice's.
Thus, we see that a program that is faster on one machine is not necessarily faster on another machine, so that comparing exact running times in order to decide which algorithm is faster is not meaningful.

The same can be said about memory usage. On a 32-bit machine, an <code>int</code> (integer data type in the C programming language) and an <code>int*</code> (a [[pointer]] to an <code>int</code>) each occupy 4 bytes of memory, whereas on a 64-bit machine, an <code>int</code> uses 4 bytes and an <code>int*</code> uses 8 bytes; so that an algorithm that uses more pointers than integers may use more memory on a 64-bit machine and less on a 32-bit machine when compared to a competing algorithm that uses more integers than pointers.

==Why the machine is now irrelevant==
The preceding section should convince you that if two programs's running times differ by at most a constant factor, then their algorithms should be considered equally efficient, as we can make one or the other faster in practice just by designing our machine accordingly. Let's now consider a case in which one algorithm can actually be faster than another.

Suppose that Alice and Bob are now given a new problem to solve and their algorithms perform as follows on ALOPEX:
{|
! N
! Alice
! Bob
|-
| 10<sup>3</sup>
| 0.040
| 0.0013
|-
| 10<sup>4</sup>
| 0.38
| 0.13
|-
| 10<sup>5</sup>
| 3.7
| 12
|-
| 10<sup>6</sup>
| 37
| 1500
|}
Observe that when we multiply the problem size by 10, Alice's program takes about 10 times longer, but Bob's program takes about 100 times longer. Thus, even though Bob's program is faster than Alice's program for small inputs (10000 lines or fewer), '''in the limit of infinite problem size''', Alice's program will ''always'' be faster. Even if we run Bob's program on a supercomputer and Alice's program on a 386, for sufficiently large input, Alice's program will always finish first, since no matter how much of a disadvantage Alice's program has, it catches up more and more as we increase the problem size; it ''scales better'' than Bob's algorithm.

Also observe that Alice's algorithm has running time approximately proportional to the size of its input, whereas Bob's algorithm has running time approximately proportional to the square of the size of its input. We write that Alice's algorithm has running time <math>\Theta(N)</math> whereas Bob's has running time <math>\Theta(N^2)</math>. Notice that we don't bother to write the constant factor, since this varies from machine to machine; we write only the part that tells us how the algorithm scales. Since <math>N^2</math> grows much more quickly than <math>N</math> as <math>N</math> increases, we see that Bob's algorithm is slower than Alice's.

==Notation==
We are now ready to give an explanation of the <math>\Theta</math>-notation used in the previous section. (See section [[#Big theta notation|Big theta notation]] below.) We suppose that functions <math>f</math> and <math>g</math> map the positive integers to the positive real numbers. The interpretation is that <math>f(n)</math> represents the amount of time (in some units) that it takes a certain algorithm to process an input of size <math>n</math> when run on a certain machine.

===Big O notation===
We say that <math>f(n) \in O(g(n))</math> when <math>g(n)</math> is asymptotically ''at least as large'' as <math>f(n)</math>. This is read ''f is big-O of g''. Mathematically, this is defined to mean that there are some constants <math>n_0, c</math> such that <math>c\cdot g(n) \geq f(n)</math> for all <math>n \geq n_0</math>; to read it idiomatically, ''for sufficiently large <math>n</math>, <math>f(n)</math> is bounded by a constant times <math>g(n)</math>.''

This means that if we plotted <math>f</math> and <math>g</math> on the same set of axes, with <math>n</math> along the positive x-axis, then we can scale the curve <math>g</math> such that it always lies above the curve <math>f</math>.

For example, if we plot <math>f(n) = 3n+1</math> and <math>g(n) = 2n+1</math> on the same set of axes, then we see that by scaling <math>g</math> by a factor of <math>\frac{3}{2}</math>, we can make the curve of <math>g</math> lie above the curve of <math>f</math>. Therefore, <math>3n+1 \in O(2n+1)</math>.

Similarly, if we plot <math>f(n) = 5n</math> and <math>g(n) = n^2</math> on the same set of axes, and we scale <math>g</math> by a factor of 5, we will make the curve of <math>g</math> lie above the curve of <math>f</math>. So <math>5n \in O(n^2)</math>.

On the other hand, if <math>f(n) = n^2</math> and <math>g(n) = 5n</math>, no matter how much we scale <math>g</math>, we cannot make it lie above <math>f</math>. We could for example try scaling <math>g</math> by a factor of 100. Then, we will have <math>f(n) \leq g(n)</math> for all <math>n</math> up to 500, but for <math>n > 500</math>, <math>f</math> will be larger. If we try scaling <math>g</math> by a factor of 1000, then <math>f</math> will still catch up at <math>n > 5000</math>, and so on. So <math>n^2 \notin O(5n)</math>.

Big O notation is the most frequently used notation for describing an algorithm's running time, since it provides an ''upper bound''. If, for example, we write that an algorithm's running time is <math>O(n^2)</math>, then this is a guarantee that, as <math>n</math> grows larger, the relative increase in the algorithm's running time is at most that of <math>n^2</math>, so that when we double <math>n</math>, our algorithm's running time will be at most quadrupled, and so on. This characterization is '''machine-independent'''; if an algorithm is <math>O(n^2)</math> on one machine then it will be <math>O(n^2)</math> on any other machine as well. (This holds true under the assumption that they are both classical von Neumann machines, which is the case for all computing machines on Earth right now.)

An algorithm that is <math>O(n^k)</math> for some constant <math>k</math> is said to be '''polynomial-time'''; its running time is bounded above by a polynomial in its input size. Polynomial-time algorithms are considered "efficient", because they provide the guarantee that as we double the problem size, the running time increases by a factor of at most <math>2^k</math>. If an algorithm is not polynomial-time, it could be that doubling the problem size from 1000 to 2000 increases the running time by a factor of 10, but doubling the problem size from 10000 to 20000 increases the running time by a factor of 100, and the factor becomes worse and worse as the problem size increases; these algorithms are considered inefficient. The first polynomial-time algorithm discovered that solves a particular problem is usually considered a breakthrough.

===Big omega notation===
Big omega notation is the opposite of big O notation. The statement that <math>f(n) \in O(g(n))</math> is equivalent to the statement that <math>g(n) \in \Omega(f(n))</math>. Conceptually, it means that <math>f(n)</math> is asymptotically at least as large as <math>g(n)</math>. Therefore, big omega notation provides a lower bound, instead of an upper bound. For example, if an algorithm's running time is <math>\Omega(k^n)</math> for some <math>k > 1</math>, then when we increase the problem size from <math>n</math> to <math>n+c</math>, the running time of our algorithm will increase by a factor of ''at least'' <math>k^c</math>. Approximately doubling the input size will then approximately ''square'' the running time. This scaling behaviour, called '''exponential time''', is considered extremely inefficient.

===Big theta notation===
If <math>f(n) \in O(g(n))</math> ''and'' <math>f(n) \in \Omega(g(n))</math>, then <math>f</math> and <math>g</math> differ by only a constant factor from each other, like the running time of Alice and Bob's algorithms from the first section. In this case, we write <math>f(n) \in \Theta(g(n))</math> or equivalently <math>g(n) \in \Theta(f(n))</math>. Whereas big O notation gives us an ''upper bound'' on a function, such as an algorithm's running time as a function of its input size, and big omega notation gives us a ''lower bound'', big theta notation gives us both simultaneously&mdash;it gives us an ''expectation'' of that function. This is often expressed as ''f is on the order of g''.

Thus, if an algorithm's running time is <math>\Theta(n^2)</math>, and we double the input size <math>n</math>, then we have an expectation that the running time of the algorithm will be nearly exactly four times what it was before, whereas big O notation would only tell us that it is not more than four times greater, and big omega notation that it is at least four times greater.

===Little O notation===
Whereas the big O notation <math>f(n) \in O(g(n))</math> expresses that <math>g</math> grows ''at least as quickly'' as <math>f</math> in an asymptotic, constant-factor-oblivious sense, little O notation, as in <math>f(n) \in o(g(n))</math>, expresses that <math>g</math> grows ''strictly more quickly'' than <math>f</math> in the limit of infinite <math>n</math>. It means that <math>\lim_{n\to\infty} \frac{f(n)}{g(n)} = 0</math>. This notation is not used very often in computer science (simply because it is rarely useful).

===Little omega notation===
Little omega notation is the opposite of little O notation; the statement that <math>f(n) \in o(g(n))</math> is equivalent to the statement that <math>g(n) \in \omega(f(n))</math>. Little omega notation, like little O notation, is rarely used in computer science.

===Tilde/swung dash===
The notation <math>f(n) \sim g(n)</math> means that <math>\lim_{n\to\infty} \frac{f(n)}{g(n)} = 1</math>. This is usually not used when discussing running times of algorithms, because it does ''not'' ignore the constant factor the way that the other notations do; hence <math>n \in \Theta(2n)</math> but <math>n \nsim 2n</math>. On the other hand, <math>n \sim n+1</math>. However, this notation may be useful when we care about the constant factor because we are quantifying something that depends on only the algorithm itself instead of the machine it runs on. For example, the amount of time an algorithm uses to sort its input depends on what machine it runs on, but the number of comparisons that the algorithm uses for a given input does not depend on the machine. In this case we might say that one algorithm requires <math>\sim N \log_2 N</math> comparisons, whereas another requires <math>\sim 2 N \log_2 N</math> comparisons. Both algorithms are <math>\Theta(N \log N)</math>, but the tilde notation distinguishes their performance.

[[Category:Pages needing diagrams]]