The online textbook readings in for this lab are optional. The lab covers the same content as Chapter 8.2, 8.3, and 8.4 but more concisely so that there’s not as much to read. You still may want to refer back to the textbook if you prefer watching videos or reading more about the topic.
Before You Begin
Pull the files for lab 7 from the skeleton.
Learning Goals
“An engineer will do for a dime what any fool will do for a dollar.”
— Paul Hilfinger
Efficiency comes in two flavors:
 Programming cost

 How long does it take to develop your programs?
 How easy is it to read or modify your code?
 How maintainable is your code?
 Execution cost

 Time complexity: How much time does your program take to execute?
 Space complexity: How much memory does your program require?
We’ve already seen many examples of reducing programming cost. We’ve written unit tests and employed testdriven development to spend a little more time up front writing tests to save a lot of time down the line debugging programs. And we’ve seen how encapsulation can help reduce the cognitive load that a programmer needs to deal with by allowing them to think in terms of highlevel abstractions like lists instead of having to deal with the nittygritty details of pointer manipulation. We’ve also discussed some elements of design for methods and classes, like how we prefer passing arguments around over maintaining static
variables.
We’ve only just scratched the surface on methods for reducing and optimizing programming costs, but for the coming weeks, it’ll be helpful to have a working understanding of the idea of execution cost.
In this lab, we consider ways of measuring the efficiency of a given code segment. Given a function f
, we want to find out how fast that function runs.
Algorithms
An algorithm is a stepbystep procedure for solving a problem, or an abstract notion that describes an approach for solving a problem. The code we write in this class, our programs, are implementations of algorithms. Indeed, we’ve already written many algorithms: the methods we’ve written for IntList
, SLList
, DLList
, and AList
are all algorithms that operate on data by storing and accessing that data in different ways.
As another example, consider the problem of sorting a list of numbers. One algorithm we might use to solve this problem is called bubble sort. Bubble sort tells us we can sort a list by repeatedly looping through the list and swapping adjacent items if they are out of order, until the entire sorting is complete.
Another algorithm we might use to solve this problem is called insertion sort. Insertion sort says to sort a list by looping through our list, taking out each item we find, and putting it into a new list in the correct order.
Several websites like VisuAlgo, Sorting.at, Sorting Algorithms, and USF have developed some animations that can help us visualize these sorting algorithms. Spend a little time playing around with these demos to get an understanding of how much time it takes for bubble sort or insertion sort to completely sort a list. We’ll revisit sorting in more detail later in this course, but for now, try to get a feeling of how long each algorithm takes to sort a list. How many comparison does each sort need? And how many swaps?
Since each comparison and each swap takes time, we want to know which is the faster algorithm: bubble sort or insertion sort? And how fast can we make our Java programs that implement them? Much of our subsequent work in this course will involve estimating program efficiency and differentiating between fast algorithms and slow algorithms. This set of activities introduces an approach to making these estimates.
Measuring Execution Time
One way to estimate the time an algorithm takes is to measure the time it takes to run the program directly. Each computer has an internal clock that keeps track of time, usually in the number of fractions of a second that have elapsed since a given base date. The Java method that accesses the clock is System.currentTimeMillis
. A Timer
class is provided in Timer.java
.
Take some time now to find out exactly what value System.currentTimeMillis
returns, and how to use the Timer
class to measure the time taken by a given segment of code.
Exercise: Sorter
The file Sorter.java
contains a version of the insertion sort algorithm mentioned earlier. Its main
method uses a commandline argument to determine how many items to sort. It fills an array of the specified size with randomly generated values, starts a timer, sorts the array, and prints the elapsed time when the sorting is finished.
javac Sorter.java
java Sorter 300
Compiling and running Sorter
like above will tell us exactly how long it takes to sort an array of 300 randomly chosen elements.
Copy Sorter.java
to your directory, compile it, and then determine the size of the smallest array that needs 1 second (1000 milliseconds) to sort. An answer within 100 elements is fine.
How fast is Sorter.java
? What’s the smallest array size that you and your partner found that takes at least 1 second to sort?
You may notice that other students in lab end up with different timing results and a different number of elements. Why are there differences between some students’ numbers and other students’ numbers? Why is it that the amount of time it takes to sort the same number of elements isn’t always the same? What might contribute to these differences?
Counting Steps
From timing the program in the previous example, we learned it isn’t very helpful in determining how good an algorithm is; different computers end up with different results! An alternative approach is step counting. The number of times a given step, or instruction, in a program gets executed is independent of the computer on which the program is run and is similar for programs coded in related languages. With step counting, we can now formally and deterministically describe the runtime of programs.
We define a single step as the execution of a single instruction or primitive function call. For example, the +
operator which adds two numbers is considered a single step. We can see that 1 + 2 + 3
can be broken down into two steps where the first is 1 + 2
while the second takes that result and adds it to 3. From here, we can combine simple steps into larger and more complex expressions.
(3 + 3 * 8) % 3
This expression takes 3 steps to complete: one for multiplication, one for addition, and one for the modulus of the result.
From expressions, we can construct statements. An assignment statement, for instance, combines an expression with one more step to assign the result of the expression to a variable.
int a = 4 * 6;
int b = 9 * (a  24) / (9  7);
In the example above, each assignment statement takes one additional step on top of however many steps it took to compute the righthand side expressions. In this case, the first assignment to a
takes one step to compute 4 * 6
and one more step to assign the result, 24, to the variable a
. How many steps does it take to finish the assignment to b
?
Here are some rules about what we count as taking a single step to compute:
 Assignment and variable declaration statements
 All unary (like negation) and binary (like addition, and, or) operators
 Conditional
if
statements  Function calls
return
statements
One important case to be aware of is that, while calling a function takes a single step to setup, executing the body of the function may require us to do much more than a single step of work.
Counting Conditionals
With conditional statements like if
statements, the total step count depends on the outcome of the condition we are testing.
if (a > b) {
temp = a;
a = b;
b = temp;
}
The example above can take four steps to execute: one for evaluating the conditional expression a > b
and three steps for evaluating each line in the body of the condition. But this is only the case if a > b
. If the condition is not true, then it only takes one step to check the conditional expression.
That leads us to consider two quantities: the worst case count, or the maximum number of steps a program can execute, and the best case count, or the minimum number of steps a program needs to execute. The worst case count for the program segment above is 4 and the best case count is 1.
if ... else
Counting
Consider an if ... else
of the form,
if (A) {
B;
} else {
C;
}
where A
, B
, and C
are program segments. (A
might be a method call, for instance.)
How many steps does it take to evaluate the entire if ... else
block in terms of the number of steps it takes to evaluate A
, B
, and C
? Think back to your practice tracing through programs to figure out which parts of the conditional will be evaluated (given the condition is true or false), and which parts won’t be evaluated.
Loop Counting
for (int k = 0; k < N; k++) {
sum = sum + 1;
}
In terms of , how many operations are executed in this loop? Remember that each of the actions in the forloop header (the initialization of k
, the exit condition, and the increment) count too!
It takes 1 step to execute the initialization,
int k = 0
. Then, to execute the loop, we have the following sequence of steps:
 Check the loop condition,
k < N
 Add 1 to the
sum
 Update the value of
sum
by assignment Increment the loop counter,
k
 Update
k
by assignmentThis accounts for the first steps. In the very last iteration of the loop, after we increment
k
such thatk
now equals , we spend one more step checking the loop condition again to figure out that we need to finally exit the loop so the final number of steps is .
Now consider code for the remove
method which removes the item at a given position of an array values
by shifting over all the remaining elements.
void remove(int pos) {
for (int k = pos + 1; k < len; k++) {
values[k  1] = values[k];
}
len = 1;
}
The counts here depend on pos
. Each column in the table below shows the total number of steps for computing each value of pos
.
category  pos = 0  pos = 1  pos = 2  …  pos = len  1 

pos + 1  1  1  1  1  
assignment to k  1  1  1  1  
loop conditional  len  len  1  len  2  1  
increment to k  len  1  len  2  len  3  0  
update k  len  1  len  2  len  3  0  
array access  len  1  len  2  len  3  0  
array assignment  len  1  len  2  len  3  0  
decrement to len  1  1  1  1  
assignment to len  1  1  1  1  
Total count  5 * len  5 * len  4  5 * len  8  5 
We can summarize these results as follows: a call to remove with argument pos
requires in total:
 1 step to calculate
pos + 1
 1 step to make the initial assignment to
k
len  pos
loop testslen  pos  1
increments ofk
len  pos  1
reassignments tok
len  pos  1
accesses tovalues
elementslen  pos  1
assignments tovalues
elements 1 step to decrement
len
 1 step to reassign to
len
If all these operations take roughly the same amount of time, the total is 5 * (len  pos)
. Notice how we write the number of statements as a function of the input argument. For a small value of pos
, the number of steps executed will be greater than if we had a larger value of pos
. And vice versa: a larger value of pos
will reduce the number of steps we need to execute.
Counting steps in nested loops is a little more involved. As an example, we’ll consider an implementation of the method removeZeroes
.
void removeZeroes() {
int k = 0;
while (k < len) {
if (values[k] == 0) {
remove(k);
} else {
k += 1;
}
}
}
Intuitively, the code should be slowest on an input where we need to do the most work, or an array of values
full of zeroes. Here, we can tell that there is a worst case—removing everything—and a best case, removing nothing. To calculate the runtime, like before, we start by creating a table to help organize information.
category  best case  worst case 

assignment to k  1  1 
loop conditional  len + 1  len + 1 
array accesses  len  len 
comparisons  len  len 
calls to remove  0  len 
k + 1  len  0 
update to k  len  0 
In the best case, we never call remove
so its runtime is simply the sum of the rows in the “best case” column. Thus, the bestcase count is 1 + 5 * len + 1
.
The only thing left to analyze is the worstcase scenario. Remember that the worst case makes len
total calls to remove
. We already approximated the cost of a call to remove
for a given pos
and len
value earlier: 5 * (len  pos)
.
In our removals, pos
is always 0, and only len
is changing. The total cost of the removals is shown below.
The challenge now is to simplify the expression. A handy summation formula to remember is the sum of the first natural numbers.
This lets us simplify the cost of removals. Remembering to include the additional steps in the table, we can now express the worstcase count of removeZeroes
as:
We often prefer to simplify this by substituting len
for a symbolic name like .
That took… a while.
Abbreviated Estimates
From this section onwards, we present a set of fairly precise definitions, and we’ll be relying on the example developed in this part and the previous part to help us build a solid definition for asymptotic notation. If you’re not fully comfortable with any of the material so far, now is the perfect time to review it with your partner or a lab assistant!
Producing step count figures for even those simple program segments took a lot of work. But normally we don’t actually need an exact step count but rather just an estimate of how many steps will be executed.
In most cases, we only care about what happens for very large as that’s where the differences between algorithms and their execution time really become limiting factors in the scalability of a program. We want to consider what types of algorithms would best handle big amounts of data, such as in the examples listed below:
 Simulation of billions of interacting particles
 Social network with billions of users
 Encoding billions of bytes of video data
The asymptotic behavior of a function f
(any one of the programs above, for example) is a description of how the execution time of f
changes as the value of grows increasingly large towards infinity. Our goal is to come up with a technique that can be used to compare and contrast two algorithms to identify which algorithm scales better for large values of .
We can then compute the order of growth of a program, a classification of how the execution time of the program changes as the size of the input grows larger and larger.
We say that the order of growth of is since, for large values of , will be less than and slightly greater than . As tends towards infinity, the contributes less and less to the overall runtime.
This pattern holds for higherorder terms too. Applying this estimation technique to the removeZeroes
method above results in the following orders of growth.
 The order of growth for the bestcase runtime of
removeZeroes
, , is proportional to the length of the array, .  The order of growth for the worstcase runtime of
removeZeroes
, , is .
The intuitive simplification being made here is that we discard all but the most significant term of the estimate and also any constant factor of that term. Later, we will see exactly why this is true with a more formal proof.
Asymptotic Analysis
Recap: Simplified Analysis Process
Rather than building the entire table of all the exact step counts, we can instead follow a simplified analysis process.
 Choose a cost model
 These are the underlying assumptions about the costs of each step or instruction for our machine. In this course, we’ll assume all of the basic operations (Java operators, assignment statements,
return
statements, array access) each take the same, 1 unit of time, but in CS 61C, we’ll see how this fundamental assumption often isn’t true.  Compute the order of growth
 Given the cost model, we can then compute the order of growth for a program. In the
removeZeroes
example, we saw how we could compute an exact count and then find the correct order of growth runtime classification for it by simplifying the expression.
Later, we’ll learn a few shortcuts and practice building intuition/inspection to determine orders of growth, but it’s helpful to remember that we’re always solving the same fundamental problem of measuring how long it takes to run a program, and how that runtime changes as we increase the value of .
BigTheta Notation
Computer scientists often use special notation to describe runtime. The first one we’ll learn is called bigtheta, represented by the symbol .
Suppose we have a function, , with order of growth . We could say,
, or “ is in ”
Why do we say “in” ? Formally, is a family of functions that all grow proportional to . Thinking back to our working definition of order of growth as a method for classification, refers to the entire set of all functions that share the same order of growth.
The advantage of using notation like bigtheta is that it provides a common definition for asymptotic analysis which reduces the amount of explaining we need to do when we want to share our ideas with others. It also makes sure we’re all on the same page with the claims we make, so long as we use them carefully and precisely.
Learning new notation can be a little daunting, but we’ve actually already been making statements in bigtheta terms. The first claim about removeZeroes
that we made earlier,
The order of growth for the bestcase runtime of
removeZeroes
, , is proportional to the length of the array, .
is essentially equivalent to the claim: In the bestcase, removeZeroes
is in .
And, likewise, the second claim that we made earlier,
The order of growth for the worstcase runtime of
removeZeroes
, , is .
has its own equivalent in bigtheta notation: In the worstcase, removeZeroes
is in .
When we use
removeZeroes
here, we mean the runtime of the function rather than the function itself. In practice, we’ll often use this English shortcut as long as the meaning is clearly communicated, though it would be more accurate to say the runtime of the function.
Asymptotic Variables
You may have observed, in our analysis of removeZeroes
, that we were careful to make clear what the running time estimate depended on, namely the value of len
and the position of the removal.
Unfortunately, students are sometimes careless about specifying the quantity on which an estimate depends. Don’t just use without making clear what means. This distinction is important especially when we begin to touch on sorting later in the course. It may not always be clear what means.
We’ll often qualify our runtimes by stating, “where is the length of the list”, but we often also say things like, “where is the value of the largest number in the list”.
Asymptotic Bounds
Formally, we say that if and only if there exist positive constants such that for all greater than some (very large ).
In other words, must be bounded above and below by asymptotically. But we’ve already seen something like this too.
We say that the order of growth of is since, for large values of , will be less than and slightly greater than . As tends towards infinity, the contributes less and less to the overall runtime.
In this example, we chose and . These two choices of constitute a tightbound for for all values of .
This idea of bigtheta notation as a tightbound is very useful as it allows us to, very precisely, state exactly how scalable a function’s runtime grows as the size of its input () grows. When a function’s input size increases, we’d expect the runtime to also increase linearly.
BigO and BigOmega
But, there are many scenarios where we can’t actually give a tight bound: sometimes, it just doesn’t exist. And, practicallyspeaking, one of the common use scenarios for runtime in the real world is to help choose between several different algorithms with different orders of growth. For these purposes, it’s often sufficient just to give an upperbound on the runtime of a program.
There exists a very common asymptotic notation, bigO, represented by the symbol, .
If we could think of bigtheta as an (equals) sign, then bigO is like a sign. Likewise, the formal definition for bigO follows, if and only if there exists a positive constant such that for all greater than some (very large ).
Note that this is a looser condition than bigtheta since bigO doesn’t include the lower bound.
Discussion: Case Analysis
Read the following three sections of Chapter 8.4 from Runtime Analysis Subtleties all the way through Big Omega. You don’t need to read the last section on Amortized Analysis.
Discuss with your partner why each of the following claims are true.
removeZeroes
is in .removeZeroes
is in .removeZeroes
is in . A bound does not exist for
removeZeroes
.  In the best case,
removeZeroes
is in .  In the best case,
removeZeroes
is in .  In the worst case,
removeZeroes
is in .  In the worst case,
removeZeroes
is in .
Limit Definition
An alternative, calculusbased limit definition is also sometimes useful, as you can apply L’Hopital’s Rule to derive asymptotic simplifications like dropping multiplicative constants and additive lowerorder terms.
We generally won’t use this too often though, as the first definition provides a more useful and intuitive visualization of the lower and upper bounds.
Common Orders of Growth
Here are some commonlyoccurring estimates listed from no growth at all to fastest growth.
 Constant time, often indicated with .
 Logarithmic time or proportional to .
 Linear time or proportional to .
 Linearithmic time or proportional to .
 Quadratic/polynomial time or proportional to .
 Exponential time or proportional to for some constant .
 Factorial time or proportional to ( factorial).
Logarithmic Algorithms
We will shortly encounter algorithms that run in time proportional to for some suitably defined . Recall from algebra that the base10 logarithm of a value is the exponent to which 10 must be raised to produce the value. It is usually abbreviated as . Thus
 is 3 because .
 is slightly less than 2 because .
 is 0 because .
In algorithms, we commonly deal with the base2 logarithm, written as , defined similarly.
 is 10 because .
 is slightly more than 3 because .
 is 0 because .
Another way to think of log is the following: is the number of times must be divided by the base before it hits 1. For the purposes of determining orders of growth, however, the log base actually doesn’t make a difference because, by the change of base formula, we know that any logarithm of is within a constant factor of any other logarithm of . We usually express a logarithmic algorithm as simply as a result.
 Change of Base Formula
Algorithms for which the running time is logarithmic are those where processing discards a large proportion of values in each iterations. The binary search algorithm is an example. We can use binary search in order to guess a number that a person in thinking. In each iteration, the algorithm discards half the possible values for the searchedfor number, repeatedly dividing the size of the problem by 2 until there is only one value left.
For example, say you started with a range of 1024 numbers in the number guessing game. Each time you would discard half of the numbers so that each round would have the following numbers under consideration:
Round #  Numbers left 

1  1024 
2  512 
3  256 
4  128 
5  64 
6  32 
7  16 
8  8 
9  4 
10  2 
11  1 
We know from above that which gives us an approximation of how many rounds it will take. We will see further applications of logarithmic behavior when we work with trees in subsequent activities.
Analyzing Iteration
We’ve thus far defined the language of asymptotic analysis and developed some simple methods based on counting the total number of steps. However, the kind of problems we want to solve are often too complex to think of just in terms of number iterations times however much work is done per iteration.
Consider the following function, repeatedSum
.
long repeatedSum(int[] values) {
int N = values.length;
long sum = 0;
for (int i = 0; i < N; i += 1) {
for (int j = i; j < N; j += 1) {
sum += values[j];
}
}
return sum;
}
In repeatedSum
, we’re given an array of values
of length N. We want to take the repeated sum over the array as defined by the following sequence of j
’s.
Notice that each time, the number of elements, or the iterations of j
, being added is reduced by 1. While in the first iteration, we sum over all elements, in the second iteration, we only sum over elements. On the next iteration, even fewer: just elements. This pattern continues until the outer loop, i
, has incremented all the way to .
One possible approach to this problem is to draw a bar chart to visualize how much work is being done for each iteration of i
. We can represent this by plotting the values of i
across the Xaxis of the chart and the number of steps for each corresponding value of i
across the Yaxis of the chart.
Now, let’s plot the amount of work being done on the first iteration of i
where i = 0
. If we examine this iteration alone, we just need to measure the amount of work done by the j
loop. In this case, the j
loop does work proportional to steps as the loop starts at 0, increments by 1, and only terminates when j = N
.
How about the next iteration of i
? The loop starts at 1 now instead of 0 but still terminates at . In this case, the j
loop is proportional to steps. The next loop, then, is proportional to steps.
We can start to see a pattern forming. As i
increases by 1, the amount of work done on each corresponding j
loop decreases by 1. As i
approaches , the number of steps in the j
loop approaches 0. In the final iteration, when i = N  1
, the j
loop performs work proportional to 1 step.
We’ve now roughly measured each loop proportional to some number of steps. Each independent bar represents the amount of work any one iteration of i
will perform. The runtime of the entire function repeatedSum
then is the sum of all the bars, or simply the area underneath the line.
The problem is now reduced to finding the area of a triangle with a base of and height of also . Thus, the runtime of repeatedSum
is in .
We can verify this result mathematically by noticing that the sequence can be described by the following summation:
or, roughly, which is in . It’s useful to know both the formula as well as its derivation through the chart above.
Analyzing Recursion
Now that we’ve learned how to use a bar chart to represent the runtime of an iterative function, let’s try the technique out on a recursive function, mitosis
.
int mitosis(int N) {
if (N == 1) {
return 1;
}
return mitosis(N / 2) + mitosis(N / 2);
}
Let’s start by trying to map each over the xaxis like we did before and try to see how much work is done for each call to the function. The conditional contributes a constant amount of work to each call. But notice that in our return statement, we make two recursive calls to mitosis
. How do we represent the runtime for these calls? We know that each call to mitosis
does a constant amount of work evaluating the conditional base case but it’s much more difficult to model exactly how much work each recursive call will do. While a bar chart is a very useful way of representing the runtime of iterative functions, it’s not always the right tool for recursive functions.
Instead, let’s try another strategy: drawing call trees. Like the charting approach we used for iteration earlier, the call tree will reduce the complexity of the problem and allow us to find the overall runtime of the program on large values of by taking the tree recursion out of the problem. Consider the call tree for fib
below.
int fib(int N) {
if (N <= 1) {
return 1;
}
return fib(n  1) + fib(n  2);
}
At the root of the tree, we make our first call to fib(n)
. The recursive calls to fib(n  1)
and fib(n  2)
are modeled as the two children of the root node. We say that this tree has a branching factor of two as each node contains two children. It takes a constant number of instructions to evaluate the conditional, addition operator, and the return statement as denoted by the 1
.
We can see this pattern occurs for all nodes in the tree: each node performs the same constant number of operations if we don’t consider recursive calls. If we can come up with a scheme to count all the nodes, then we can simply multiply by the constant number of operations to find the overall runtime of fib
.
Remember that the number of nodes in a tree is calculated as the branching factor, , raised to the height of the tree, , or . Spend a little time thinking about the maximum height of this tree: when does the base case tell us the tree recursion will stop?
Returning to the original problem of mitosis
, the call tree is setup just like fib
except instead of decrementing by 1 or 2, we now divide in half each time. Each node performs a constant amount of work but also makes two recursive calls to mitosis(N / 2)
.
Like before, we want to identify both the branching factor and the height of the tree. In this case, the branching factor is 2 like before. Recall that the series contains elements since, if we start at and break the problem down in half each time, it will take us approximately steps to completely reduce down to 1.
Plugging into the formula, we get nodes which simplifies to . Therefore, nodes performing a constant amount of work each will give us an overall runtime in .
In general, for a recursion tree, we can think of the total work as For mitosis
, we have layers, nodes in layer , with work per node. Thus we see the sumation , which is exactly the quantity we just calculated.
Recap
 Runtime Minimization
 One of the most important properties of a program is the time it takes to execute. One goal as a programmer is to minimize the time (in seconds) that a program takes to complete.
 Runtime Measurement

 Measure the number of seconds that a program takes to complete using a stopwatch (either physical or in software). This tells you the actual runtime, but is dependent on the machine and inputs.
 Count the number of operations needed for inputs of a given size. This is a machine independent analysis, but still depends on the input, and also doesn’t actually tell you how long the code takes to run.
 Derive an algebraic expression relating the number of operations to the size of an input. This tells you how the algorithm scales, but does not tell you how long the code takes to run.
 Algorithm Scaling
 While we ultimately care about the runtime of an algorithm in seconds, we’ll often say that one algorithm is better than another simply because of how it scales. By scaling, we mean how the runtime of a piece of code grows as a function of its input size. For example, inserting at the beginning of ArrayList on an old computer might take seconds, where is the size of the list.
For example, if the runtime of two algorithms is , and , we’d say algorithm is better, even though is much faster for small .
 Order of Growth
 The result of applying our last 3 simplifications gives us the order of growth of a function. So for example, suppose , we’d say that the order of growth of is .
The terms “constant”, “linear”, and “quadratic” are often used for algorithms with order of growth , , and , respectively. For example, we might say that an algorithm with runtime is quadratic.
 Simplified Analysis
 Once we’ve chosen a cost model, we can either:
 Compute the exact expression that counts the number of operations.
 Use intuition and inspection to find the order of growth of the number of operations.
This latter approach is generally preferable, but requires a lot of practice. One common intuitive/inspectionbased approach is use geometric intuition. For example, if we have nested for loops where i goes from 0 to N, and j goes from i + 1 to N, we observe that the runtime is effectively given by a right triangle of side length N. Since the area of a such a triangle grows quadratically, the order of growth of the runtime is quadratic.
 BigTheta
 To formalize our intuitive simplifications, we introduce bigtheta notation. We say that a function if there exists positive constants and such that .
When using to capture a function’s asymptotic scaling, we avoid unnecessary terms in our expression. For example, while , we will usually make the simpler claim that is .
Bigtheta is exactly equivalent to order of growth. That is, if a function has order of growth , then we also have that .
In the final section, we applied what we learned about counting steps, estimation, and orders of growth to model algorithmic analysis for larger problems. Two techniques, charting and drawing call trees, helped us break down challenging problems into smaller pieces that we could analyze individually and recombine to form the final solution.
Below, we will list some tips and formulas that will be handy when you start finding the asymptotic runtimes of functions.
Practical Tips
 Before attempting to calculate a function’s runtime, first try to understand what the function does.
 Try some small sample inputs to get a better intuition of what the function’s runtime is like. What is the function doing with the input? How does the runtime change as the input size increases? Can you spot any ‘gotchas’ in the code that might invalidate our findings for larger inputs?
 Try to lower bound and upper bound the function runtime given what you know about how the function works. This is a good sanity check for your later observations.
 If the function is recursive, draw a call tree to map out the recursive calls. This breaks the problem down into smaller parts that we can analyze individually. Once each part of the tree has been analyzed, we can then reassemble all the parts to determine the overall runtime of the function.
 If the function has a complicated loop, draw a bar chart to map out how much work the body of the loop executes for each iteration.
Useful Formulas
 is in .
 There are terms in the sequence .
 is in .
 There are terms in the sequence .
 The number of nodes in a complete tree, , is equal to where is the branching factor and is the height of the tree.
 All logarithms are proportional to each other by the Change of Base formula so we can express them generally as just .
It’s worth spending a little time proving each of these to yourself with a visual model!
Deliverables
A quick recap of what you need to do to finish today’s lab.
 Look through the
Timer
class and try timing the algorithm inSorter.java
for different inputs. Discuss with your neighbors what you and your partner came up with.  Read through the content on asymptotic analysis (bigtheta, O, and omega) focusing on how to handle logarithmic, iterative, and recursive algorithms.
 Complete the online assessment on Gradescope. There is no coding submission.