1 / 79

CSCI-2500: Computer Organization

CSCI-2500: Computer Organization. Computer Abstractions, Technology and History. The Computer Revolution. §1.1 Introduction. Progress in computer technology Underpinned by Moore ’ s Law Makes novel applications feasible Computers in automobiles Cell phones Human genome project

hector-andrews
Télécharger la présentation

CSCI-2500: Computer Organization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSCI-2500:Computer Organization Computer Abstractions, Technology and History

  2. The Computer Revolution §1.1 Introduction • Progress in computer technology • Underpinned by Moore’s Law • Makes novel applications feasible • Computers in automobiles • Cell phones • Human genome project • World Wide Web • Search engines • Computers are pervasive CSCI-2500 FALL 2012, Ch1, P&H — 2

  3. Bill Gates “joke” • At a computer expo (COMDEX), Bill Gates reportedly compared the computer industry with the auto industry and stated that :- • "If GM had kept up with technology like the computer industry has, we would all be driving twenty-five dollar cars that got 1000 miles to the gallon." CSCI-2500 FALL 2012, Ch1, P&H — 2

  4. GM’s “joke” response! • In response to Gates' comments, General Motors issued a press release stating:If GM had developed technology like Microsoft, we would all be driving cars with the following characteristics:1. For no reason whatsoever your car would crash twice a day.2. Every time they repainted the lines on the road you would have to buy a new car.3. Occasionally your car would die on the freeway for no reason, and you would just accept this, restart and drive on.4. Occasionally, executing a maneuver such as a left turn, would cause your car to shut down and refuse to restart, in which case you would have to reinstall the engine.5. Only one person at a time could use the car, unless you bought "Car95" or "CarNT". But then you would have to buy more seats.6. Macintosh/Apple would make a car that was powered by the sun, reliable, five times as fast, and twice as easy to drive, but would only work on five percent of the roads. CSCI-2500 FALL 2012, Ch1, P&H — 2

  5. GM “joke” continues… • 7. The oil, water temperature and alternator warning lights would be replaced by a single "general car default" warning light.8. New seats would force everyone to have the same size butt.9. The airbag system would say "Are you sure?" before going off.10. Occasionally for no reason whatsoever, your car would lock you out and refuse to let you in until you simultaneously lifted the door handle, turned the key, and grab hold of the radio antenna.11. GM would require all car buyers to also purchase a deluxe set of Rand McNally road maps (now a GM subsidiary), even though they neither need them nor want them. Attempting to delete this option would immediately cause the car's performance to diminish by 50% or more. Moreover, GM would become a target for investigation by the Justice Department.12. Every time GM introduced a new model car buyers would have to learn to drive all over again because none of the controls would operate in the same manner as the old car.13. You'd press the "start" button to shut off the engine. CSCI-2500 FALL 2012, Ch1, P&H — 2

  6. Lesson… • So, while computers have improved in performance vastly over the last 50 years, other “usability” aspects of computers remain open problems • …but this is comp org and so we’ll focus a great deal on computer system performance… • Note, this exchange is Internet “lore” • See:http://www.snopes.com/humor/jokes/autos.asp CSCI-2500 FALL 2012, Ch1, P&H — 2

  7. Classes of Computers • Desktop computers • General purpose, variety of software • Subject to cost/performance tradeoff • Server computers • Network based • High capacity, performance, reliability • Range from small servers to building sized • Embedded computers • Hidden as components of systems • Stringent power/performance/cost constraints CSCI-2500 FALL 2012, Ch1, P&H — 2

  8. The Processor Market CSCI-2500 FALL 2012, Ch1, P&H — 2

  9. Topics You Will Learn • Process by which programs are translated into the machine language • And how the hardware executes them • The hardware/software interface • Factors that determine program performance • And how it can be improved • Approaches to improving performance • Multicore parallel processing CSCI-2500 FALL 2012, Ch1, P&H — 2

  10. Understanding Performance • Algorithm • Determines number of operations executed • Programming language, compiler, architecture • Determine number of machine instructions executed per operation • Processor and memory system • Determine how fast instructions are executed • I/O system (including OS) • Determines how fast I/O operations are executed CSCI-2500 FALL 2012, Ch1, P&H — 2

  11. Below Your Program • Application software • Written in high-level language • System software • Compiler: translates HLL code to machine code • Operating System: service code • Handling input/output • Managing memory and storage • Scheduling tasks & sharing resources • Hardware • Processor, memory, I/O controllers §1.2 Below Your Program CSCI-2500 FALL 2012, Ch1, P&H — 2

  12. Levels of Program Code • High-level language • Level of abstraction closer to problem domain • Provides for productivity and portability • Assembly language • Textual representation of instructions • Hardware representation • Binary digits (bits) • Encoded instructions and data CSCI-2500 FALL 2012, Ch1, P&H — 2

  13. Breaking down the hierarchy • High-level code becomes a collection of: • Data movement operations • Compute operations • Program flow CSCI-2500 FALL 2012, Ch1, P&H — 2

  14. Components of a Computer • Same components forall kinds of computer • Desktop, server,embedded • Input/output includes • User-interface devices • Display, keyboard, mouse • Storage devices • Hard disk, CD/DVD, flash • Network adapters • For communicating with other computers The BIG Picture CSCI-2500 FALL 2012, Ch1, P&H — 2

  15. Anatomy of a Computer Output device Network cable Input device Input device CSCI-2500 FALL 2012, Ch1, P&H — 2

  16. Anatomy of a Mouse • Optical mouse • LED illuminates desktop • Small low-res camera • Basic image processor • Looks for x, y movement • Buttons & wheel • Supersedes roller-ball mechanical mouse CSCI-2500 FALL 2012, Ch1, P&H — 2

  17. Opening the Box CSCI-2500 FALL 2012, Ch1, P&H — 2

  18. Inside the Processor (CPU) • Datapath: performs operations on data • Control: sequences datapath, memory, … • Cache memory • Small fast SRAM memory for immediate access to data CSCI-2500 FALL 2012, Ch1, P&H — 2

  19. Inside the Processor • AMD Barcelona: 4 processor cores CSCI-2500 FALL 2012, Ch1, P&H — 2

  20. Abstractions • Abstraction helps us deal with complexity • Hide lower-level detail • Instruction set architecture (ISA) • The hardware/software interface • Application binary interface (ABI) • The ISA plus system software interface • Implementation • The underlying details and interface The BIG Picture CSCI-2500 FALL 2012, Ch1, P&H — 2

  21. A Safe Place for Data • Volatile main memory • Loses instructions and data when power off • Non-volatile secondary memory • Magnetic disk • Flash memory • Optical disk (CDROM, DVD) CSCI-2500 FALL 2012, Ch1, P&H — 2

  22. Networks • Communication and resource sharing • Local area network (LAN): Ethernet • Within a building • Wide area network (WAN): the Internet • Wireless network: WiFi, Bluetooth CSCI-2500 FALL 2012, Ch1, P&H — 2

  23. Technology Trends • Electronics technology continues to evolve • Increased capacity and performance • Reduced cost DRAM capacity CSCI-2500 FALL 2012, Ch1, P&H — 2

  24. Defining Performance §1.4 Performance • Which airplane has the best performance? CSCI-2500 FALL 2012, Ch1, P&H — 2

  25. Response Time and Throughput • Response time • How long it takes to do a task • Throughput • Total work done per unit time • e.g., tasks/transactions/… per hour • How are response time and throughput affected by • Replacing the processor with a faster version? • Adding more processors? • We’ll focus on response time for now… CSCI-2500 FALL 2012, Ch1, P&H — 2

  26. Relative Performance • Define Performance = 1/Execution Time • “X is n times faster than Y” • Example: time taken to run a program • 10s on A, 15s on B • Execution TimeB / Execution TimeA= 15s / 10s = 1.5 • So A is 1.5 times faster than B CSCI-2500 FALL 2012, Ch1, P&H — 2

  27. Measuring Execution Time • Elapsed time • Total response time, including all aspects • Processing, I/O, OS overhead, idle time • Determines system performance • CPU time • Time spent processing a given job • Discounts I/O time, other jobs’ shares • Comprises user CPU time and system CPU time • Different programs are affected differently by CPU and system performance CSCI-2500 FALL 2012, Ch1, P&H — 2

  28. CPU Clocking • Operation of digital hardware governed by a clock, which can change to save power Clock period Clock (cycles) Data transferand computation Update state • Clock period: duration of a clock cycle • e.g., 250ps = 0.25ns = 250×10–12s • Clock frequency (rate): cycles per second • e.g., 4.0GHz = 4000MHz = 4.0×109Hz = 4 GHz CSCI-2500 FALL 2012, Ch1, P&H — 2

  29. CPU Time • Performance improved by • Reducing number of clock cycles • Increasing clock rate • Hardware designer must often trade off clock rate against cycle count CSCI-2500 FALL 2012, Ch1, P&H — 2

  30. CPU Time Example • Computer A: 2GHz clock, 10s CPU time • Designing Computer B • Aim for 6s CPU time • Can do faster clock, but causes 1.2 × clock cycles • How fast must Computer B clock be? CSCI-2500 FALL 2012, Ch1, P&H — 2

  31. Instruction Count and CPI • Instruction Count for a program • Determined by program, ISA and compiler • Average cycles per instruction • Determined by CPU hardware • If different instructions have different CPI • Average CPI affected by instruction mix CSCI-2500 FALL 2012, Ch1, P&H — 2

  32. CPI Example • Computer A: Cycle Time = 250ps, CPI = 2.0 • Computer B: Cycle Time = 500ps, CPI = 1.2 • Same ISA • Which is faster, and by how much? A is faster… …by this much CSCI-2500 FALL 2012, Ch1, P&H — 2

  33. CPI in More Detail • If different instruction classes take different numbers of cycles • Weighted average CPI Relative frequency CSCI-2500 FALL 2012, Ch1, P&H — 2

  34. CPI Example • Alternative compiled code sequences using instructions in classes A, B, C • Sequence 1: IC = 5 • Clock Cycles= 2×1 + 1×2 + 2×3= 10 • Avg. CPI = 10/5 = 2.0 • Sequence 2: IC = 6 • Clock Cycles= 4×1 + 1×2 + 1×3= 9 • Avg. CPI = 9/6 = 1.5 CSCI-2500 FALL 2012, Ch1, P&H — 2

  35. Performance Summary • Performance depends on • Algorithm: affects IC, possibly CPI • Programming language: affects IC, CPI • Compiler: affects IC, CPI • Instruction set architecture: affects IC, CPI, Tc The BIG Picture CSCI-2500 FALL 2012, Ch1, P&H — 2

  36. Power Trends §1.5 The Power Wall • In CMOS IC technology ×30 5V → 1V ×1000 CSCI-2500 FALL 2012, Ch1, P&H — 2

  37. Reducing Power • Suppose a new CPU has • 85% of capacitive load of old CPU • 15% voltage and 15% frequency reduction • The power wall • We can’t reduce voltage further • We can’t remove more heat • How else can we improve performance? CSCI-2500 FALL 2012, Ch1, P&H — 2

  38. Uniprocessor Performance §1.6 The Sea Change: The Switch to Multiprocessors Constrained by power, instruction-level parallelism, memory latency CSCI-2500 FALL 2012, Ch1, P&H — 2

  39. Multiprocessors • Multicore microprocessors • More than one processor per chip • Requires explicitly parallel programming • Compare with instruction level parallelism • Hardware executes multiple instructions at once • Hidden from the programmer • Hard to do • Programming for performance • Load balancing • Optimizing communication and synchronization CSCI-2500 FALL 2012, Ch1, P&H — 2

  40. Manufacturing ICs • Yield: proportion of working dies per wafer §1.7 Real Stuff: The AMD Opteron X4 CSCI-2500 FALL 2012, Ch1, P&H — 2

  41. AMD Opteron X2 Wafer • X2: 300mm wafer, 117 chips, 90nm technology • X4: 45nm technology CSCI-2500 FALL 2012, Ch1, P&H — 2

  42. Integrated Circuit Cost • Nonlinear relation to area and defect rate • Wafer cost and area are fixed • Defect rate determined by manufacturing process • Die area determined by architecture and circuit design CSCI-2500 FALL 2012, Ch1, P&H — 2

  43. SPEC CPU Benchmark • Programs used to measure performance • Supposedly typical of actual workload • Standard Performance Evaluation Corp (SPEC) • Develops benchmarks for CPU, I/O, Web, … • SPEC CPU2006 • Elapsed time to execute a selection of programs • Negligible I/O, so focuses on CPU performance • Normalize relative to reference machine • Summarize as geometric mean of performance ratios • CINT2006 (integer) and CFP2006 (floating-point) CSCI-2500 FALL 2012, Ch1, P&H — 2

  44. CINT2006 for Opteron X4 2356 High cache miss rates CSCI-2500 FALL 2012, Ch1, P&H — 2

  45. SPEC Power Benchmark • Power consumption of server at different workload levels • Performance: ssj_ops/sec • Power: Watts (Joules/sec) CSCI-2500 FALL 2012, Ch1, P&H — 2

  46. SPECpower_ssj2008 for X4 CSCI-2500 FALL 2012, Ch1, P&H — 2

  47. Pitfall: Amdahl’s Law • Improving an aspect of a computer and expecting a proportional improvement in overall performance §1.8 Fallacies and Pitfalls • Example: multiply accounts for 80s/100s • How much improvement in multiply performance to get 5× overall? • Can’t be done! • Corollary: make the common case fast CSCI-2500 FALL 2012, Ch1, P&H — 2

  48. Fallacy: Low Power at Idle • Look back at X4 power benchmark • At 100% load: 295W • At 50% load: 246W (83%) • At 10% load: 180W (61%) • Google data center • Mostly operates at 10% – 50% load • At 100% load less than 1% of the time • Consider designing processors to make power proportional to load CSCI-2500 FALL 2012, Ch1, P&H — 2

  49. Pitfall: MIPS as a Performance Metric • MIPS: Millions of Instructions Per Second • Doesn’t account for • Differences in ISAs between computers • Differences in complexity between instructions • CPI varies between programs on a given CPU CSCI-2500 FALL 2012, Ch1, P&H — 2

  50. History: The Beginning… • ENIAC – ~1940s, First Electronic Computer • Built @ UPenn by Eckert and Mauchly • ENIAC  Electronic Numerical Integrator and Calculator • HUGE!  80 feet long, 8.5 feet high and a couple of feet wide. • Each of the 20, 10 bit registers where 2 ft long. • Had a total of 18,000 vacuum tubes • Used to compute artillery firing tables CSCI-2500 FALL 2012, Ch1, P&H — 2

More Related