lect3 performance

lect3 performance - The bottom line: Performance Car Time...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
CSE 141 Dean Tullsen Measuring and Discussing Computer System Performance or “My computer is faster than your computer” CSE 141 Dean Tullsen The bottom line: Performance ° Time to do the task , response time, latency ° Tasks per day, hour, week, sec, ns. . . , bandwidth Car Ferrari Greyhound Speed 160 mph 65 mph Time to Bay Area 3.1 hours 7.7 hours Passengers 2 60 Throughput (pmph) 320 3900 CSE 141 Dean Tullsen How to measure Execution Time? Wall-clock time? user CPU time? user + kernel CPU time? Answer: % time program ... program results . .. 90.7u 12.9s 2:39 65% % CSE 141 Dean Tullsen Our definition of Performance only has meaning in the context of a or Not very intuitive as an absolute measure, but most of the time we’re more interested in relative performance . Performance X = 1 Execution Time X , for program X
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CSE 141 Dean Tullsen Relative Performance, the Definition Performance X Execution Time X Performance Y Relative Performance Execution Time Y === n (X/Y) CSE 141 Dean Tullsen Example
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/14/2008 for the course CSE 141 taught by Professor Tullsen during the Fall '06 term at UCSD.

Page1 / 5

lect3 performance - The bottom line: Performance Car Time...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online