Big O and Algorithms (Part 1)

Post on 30-Dec-2015

21 views 2 download

Tags:

description

Big O and Algorithms (Part 1). b y Google today. Discrete Structures (CS 173) Madhusudan Parthasarathy, University of Illinois. Announcements. Midterm 2: how did it go? All the usual homeworks due this week. This week. How do we characterize the computational cost of an algorithm? - PowerPoint PPT Presentation

transcript

Big O and Algorithms (Part 1)

Discrete Structures (CS 173)Madhusudan Parthasarathy, University of Illinois 1

by Google today

Announcements

• Midterm 2: how did it go?

• All the usual homeworks due this week

2

This week

• How do we characterize the computational cost of an algorithm?

• How do we compare the speed of two algorithms?

• How do we compute cost based on code or pseudocode?

3

Today

• How do we characterize the computational cost of an algorithm?

• How do we compare the speed of two algorithms?

• How do we compute cost based on code or pseudocode?

4

How should we think about an algorithm’s computational cost?

• Time taken?

• Number of instructions called?

• Expected time as a function of the inputs?

• How quickly the cost grows as a function of the inputs

5

Example: Finding smallest m valuesoutput = findmin(input, m) % returns m smallest inputs

for each ith output (there are m of these) for each jth input (there are n of these)

if j is not used and input(j) < output(i) output(i) = input(j);

j_out = j; end end mark that j_out has been used as an outputendreturn output

6See findmin.m

Example: Finding smallest m values

minvals = findmin(vals, m)

7

Constants that depend on implementation details, architecture, etc.

Dominant factor

Key ideas in runtime analysis

1. Model how algorithm speed depends on the size of the input/parameters– Ignore factors that depend on architecture or details of compiled

code

2. We care mainly about asymptotic performance– If the input size is small, we’re not usually worried about speed

anyway

3. We care mainly about dominant terms– An algorithm that takes time takes almost as long (as a ratio) as

one that takes time if is large

8

Asymptotic relationships

9If , then for non-zero

Ordering of functions

10

11

12

Example: comparing findmin algorithms

13

output = findmin(input, m) % can be implemented different ways

for each ith output (there are m of these) for each jth input (there are n of these)

if j is not used and input(j) < output(i) output(i) = input(j);

j_out = j; end end mark that j_out has been used as an outputendreturn output

output = findmin_sort(input, m)sorted_input = sort(input, ascending);output = sorted_input(1…m);

Big-O: motivation

14

Big-O is iff there are such that for every

O(

15

16

is if is and is

17

Proving Big-O with inductionClaim: is Definition: is iff there are such that

for every .Choose and : ,

Proof: Suppose is an integer. I need to show for . I will use induction on .Base case: Induction: Suppose for . We need to show .

18

Things to remember• Model algorithm complexity in terms of how much the cost increases as the

input/parameter size increases

• In characterizing algorithm computational complexity, we care about– Large inputs– Dominant terms

• if the dominant terms in are equivalent or dominated by the dominant terms in

• if the dominant terms in are equivalent to those in

19

Next class• Analyzing pseudocode

20