DOCSLIB.ORG

5.4 Winmemmanaginternals [Read-Only]

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
5.4 Winmemmanaginternals [Read-Only] Unit OS5: Memory Management 5.4. Windows Memory Management Internals Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze Copyright Notice © 2000-2005 David A. Solomon and Mark Russinovich These materials are part of the Windows Operating System Internals Curriculum Development Kit, developed by David A. Solomon and Mark E. Russinovich with Andreas Polze Microsoft has licensed these materials from David Solomon Expert Seminars, Inc. for distribution to academic organizations solely for use in academic environments (and not for commercial use) Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 2 1 Roadmap for Section 5.4. From working sets to paging dynamics Birth of a process working set Working set trimming, heuristics Paging, paging dynamics Hard vs. soft page faults Page files Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 3 All* Committed Virtual Address Space is Mapped to Files Ranges of virtual address space are mapped to ranges of blocks w ithin disk files Each such range is defined by a “section object” (visible in WinObj if named) These files are the “backing store” for virtual address space Commonly-used files are: The system paging file For writeable, nonshareable (copy -on-write) pages i.e. most writeable data For read-only application-defined code and for shareable data Executable program or DLL Can set up additional file/virtual address space relationships at run time (CreateFileMapping API) *almost - exceptions include nonpaged pool & system code mapped into each user process and/or physical memory allocated through new Windows 2000 extended addressing services 2 Application Startup Maps V.A.S. to Code on Disk 00000000 paging file .dll .exe 7FFFFFFF See link/dump/header, or QuickView for .exe’s and .dll’s CreateFileMapping, MapViewOfFile simply make the mechanism available to application-level code All of these files may simultaneously be mapped by other processes Working Set Working set: All the physical pages “owned” by a process Essentially, all the pages the process can reference without incurring a page fault Working set limit: The maximum pages the process can own When limit is reached, a page must be released for every page that’s brought in (“working set replacement”) Default upper limit on size for each process System-wide maximum calculated & stored in MmMaximumWorkingSetSize approximately RAM minus 512 pages (2 MB on x86) minus min size of system working set (1.5 MB on x86) Interesting to view (gives you an idea how much memory you’ve “lost” to the OS) True upper limit: 2 GB minus 64 MB 3 Working Set List newer pages older pages PerfMon Process “WorkingSet” A process always starts with an empty working set It then incurs page faults when referencing a page that isn’t in its working set Many page faults may be resolved from memory (to be described later) Birth of a Working Set Pages are brought into memory as a result of page faults Prior to XP, no pre-fetching at image startup But readahead is performed after a fault See MmCodeClusterSize, MmDataClusterSize, MmReadClusterSize If the page is not in memory, the appropriate block in the associated file is read in Physical page is allocated Block is read into the physical page Page table entry is filled in Exception is dismissed Processor re-executes the instruction that caused the page fault (and this time, it succeeds) The page has now been “faulted into” the process “working set” 4 Prefetch Mechanism First 10 seconds of file activity is traced and used to prefetch data the next time Also done at boot time (described in Startup/Shutdown section) Prefetch “trace file” stored in \Windows\Prefetch Name of .EXE-<hash of full path>.pf When application run again, system automatically Reads in directories referenced Reads in code and file data Reads are asynchronous But waits for all prefetch to complete Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 9 Prefetch Mechanism In addition, every 3 days, system automatically defrags files involved in each application startup Bottom line: Reduces disk head seeks This was seen to be the major factor in slow application/system startup Lab Run Filemon – set filter as Notepad.exe Make a temporary directory somewhere (e.g. \temp) Run “Notepad \temp\x.y” Exit Notepad Run Notepad again In Filemon log, find creation of .PF file after first run, then use of new .PF in 2nd run Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 10 5 Working Set Replacement PerfMon Process “WorkingSet” When working set max reached (or working set trim occurs), must give up pages to make room for new pages to standby Local page replacement policy (most Unix systems implement global replacement) or modified Means that a single process cannot take over all of physical memory unless other page list processes aren’t using it Page replacement algorithm is least recently accessed (pages are aged) On UP systems only in Windows 2000 – done on all systems in Windows XP/Server 2003 New VirtualAlloc flag in XP/Server 2003: MEM_WRITE_WATCH Soft vs. Hard Page Faults Types of “soft” page faults: Pages can be faulted back into a process from the standby and modified page lists A shared page that’s valid for one process can be faulted into other processes Some hard page faults unavoidable Process startup (loading of EXE and DLLs) Normal file I/O done via paging Cached files are faulted into system working set To determine paging vs. normal file I/Os: Monitor Memory->Page Reads/sec Not Memory->Page Faults/sec, as that includes soft page faults Subtract System->File Read Operations/sec from Page Reads/sec Or, use Filemon to determine what file(s) are having paging I/O (asterisk next to I/O function) Should not stay high for sustained period 6 Viewing the Working Set Working set size counts shared pages in each working set Vadump (Resource Kit) can dump the breakdown of private, shareable, and shared pages C:\> Vadump –o –p 3968 Module Working Set Contributions in pages Total Private Shareable Shared Module 14 3 11 0 NOTEPAD.EXE 46 3 0 43 ntdll.dll 36 1 0 35 kernel32.dll 7 2 0 5 comdlg32.dll 17 2 0 15 SHLWAPI.dll 44 4 0 40 msvcrt.dll Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 13 Working Set System Services Min/Max set on a per-process basis Can view with !process in Kernel Debugger System call below can adjust min/max, but has minimal effect prior to Server 2003 Limits are “soft” (many processes larger than max) Memory Manager decides when to grow/shink working sets New system call in Server 2003 (SetProcessWorkingSetSizeEx) allows setting hard min/max Can also self-initiate working set trimming Pass -1, -1 as min/max working set size (minimizing a window does this for you) Windows API: SetProcessWorkingSetSize( HANDLE hProcess, DWORD dwMinimumWorkingSetSize, DWORD dwMaximumWorkingSetSize) 7 Locking Pages Pages may be locked into the process working set Pages are guaranteed in physical memory (“resident”) when any thread in process is executing Windows API: status = VirtualLock(baseAddress, size); status = VirtualUnlock(baseAddress, size); Number of lockable pages is a fraction of the maximum working set size Changed by SetProcessWorkingSetSize Pages can be locked into physical memory (by kernel mode code only) Pages are then immune from “outswapping” as well as paging MmProbeAndLockPages Process Memory Information Task Manager 1 2 Processes tab 1u “Mem Usage” = physical memory used by process (working set size, not working set limit) u Note: shared pages are counted in each process 2u “VM Size” = private (not shared) committed virtual space in processes == process’s paging file allocation 3u “Mem Usage” in status bar is not total of “Mem Usage” column (see later slide) 3 Screen snapshot from: Task Manager | Processes tab 8 Process Memory Information PerfMon - Process Object 7 “Virtual Bytes” = committed + reserved virtual space, including shared pages 1 “Working Set” = working set size (not limit) (physical) 2 “Private Bytes” = private virtual space (same as “VM Size” from Task Manager Processes list) Also: In Threads object, look for threads in Transition state - evidence of swapping (usually caused by severe memory 2 pressure) 7 1 Screen snapshot from: Performance Monitor counters from Process object Balance Set Manager Nearest thing NT has to a “swapper” Balance set = sum of all inswapped working sets Balance Set Manager is a system thread Wakes up every second. If paging activity high or memory needed: trims working sets of processes if thread in a long user-mode wait, marks kernel stack pages as pageable if process has no nonpageable kernel stacks, “outswaps” process triggers a separate thread to do the “outswap” by gradually reducing target process’s working set limit to zero Evidence: Look for threads in “Transition” state in PerfMon Means that kernel stack has been paged out, and thread is waiting for memory to be allocated so it can be paged back in This thread also performs a scheduling-related function CPU starvation avoidance - already covered 9 Process Exploder Memory Information for a Process Virtual sizes of committed sections of image and DLLs or total of all (total selected) Virtual sizes of sections mapped after image startup (including DLLs loaded with LoadLibrary) Process-private committed virtual address space (i.e. paging file allocation) note, “writecopy” = “writeable, but not written to yet”. NT has yet to create process-private pages for these; they are still shared; they become “private commit” when written to Some, but not all, of this info is also shown by Process Viewer’s “memory detail” button Windows Operating System Internals - by David A.
Load more

Recommended publications
  • System Administration Guide
    Experion PKS Release 516 System Administration Guide EPDOC-X139-en-516A August 2020 DISCLAIMER This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright 2020 - Honeywell International Sàrl 2 Contents CONTENTS Contents 3 Chapter 1 - About this guide 9 Before reading this guide 10 Chapter 2 - System administration 11 Administering users 12 Windows user accounts 12 Users and groups 12 Passwords administration 13 Deleting a user 13 Experion Operator accounts 14 Control Builder client licenses 14 Administering displays 15 Changing service account passwords 16 Service account scope types 18 Changing passwords for single-machine scope accounts 21 Changing passwords for multi-machine scope accounts 22 Preparing to change passwords for system-wide scope accounts 23 Changing passwords for system-wide scope accounts 26 Changing DSA Advanced Security
    [Show full text]
  • Deploying Microsoft SQL Server on Amazon Web Services
    Deploying Microsoft SQL Server on Amazon Web Services This paper has been archived. November 2019 For the latest technical content about the AWS Cloud, see the AWS Whitepapers & Guides page: https://aws.amazon.com/whitepapers Archived Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Archived Contents Introduction .......................................................................................................................... 1 Amazon RDS for SQL Server .......................................................................................... 1 SQL Server on Amazon EC2 ........................................................................................... 1 Hybrid Scenarios .............................................................................................................. 2 Choosing Between
    [Show full text]
  • Copyrighted Material
    Index Numerics Address Resolution Protocol (ARP), 1052–1053 admin password, SOHO network, 16-bit Windows applications, 771–776, 985, 1011–1012 900, 902 Administrative Tools window, 1081–1083, 32-bit (x86) architecture, 124, 562, 769 1175–1176 64-bit (x64) architecture, 124, 562, 770–771 administrative tools, Windows, 610 administrator account, 1169–1170 A Administrators group, 1171 ADSL (Asynchronous Digital Subscriber Absolute Software LoJack feature, 206 Line), 1120 AC (alternating current), 40 Advanced Attributes window, NTFS AC adapters, 311–312, 461, 468–469 partitions, 692 Accelerated Graphics Port (AGP), 58 Advanced Computing Environment (ACE) accelerated video cards (graphics initiative, 724 accelerator cards), 388 Advanced Confi guration and Power access points, wireless, 996, 1121 Interface (ACPI) standard, 465 access time, hard drive, 226 Advanced Graphics Port (AGP) card, access tokens, 1146–1147 391–392 Account Operators group, 1172 Advanced Graphics Port (AGP) port, 105 ACE (Advanced Computing Environment) Advanced Host Controller Interface (AHCI), initiative, 724 212–213 ACPI (Advanced Confi guration and Power Advanced Micro Devices (AMD), 141–144 Interface) standard, 465 Advanced Packaging Tool (APT), 572 Action Center, 1191–1192 Advanced Power Management (APM) Active Directory Database, 1145–1146, 1183 standard, 465 active heat sink, 150 Advanced Programmable Interrupt active matrix display, LCD (thin-fi lm Controller (APIC), 374 transistor (TFT) display), 470 Advanced RISC Computing Specifi cation active partition, 267,
    [Show full text]
  • Windows NT Network Management: Reducing Total Cost of Ownership - 9 - Performance Monitoring
    Windows NT ...: Reducing Total Cost of Ownership - Chapter 9 - Performance Monitorin Page 1 of 13 [Figures are not included in this sample chapter] Windows NT Network Management: Reducing Total Cost of Ownership - 9 - Performance Monitoring AN OLD ADAGE SAYS, "IF YOU can’t measure it, you can’t manage it." Even if you can measure something, how can you tell if your changes are making a difference if you don’t have baseline information? It’s important to monitor a server’s or work- station’s performance to maximize your investment in these tools. If a user complains that her computer is too slow, you often need more information to fix the problem. For example, if the problem is loading Web pages on a computer using an analog modem, the modem is probably limiting the system’s performance. However, if the computer is an older model, certain operations may wait for the CPU to finish processing. In this case, a complete system upgrade may be the best solution. The usefulness of performance monitoring goes far beyond handling user expectations. A network and systems administrator can use information obtained by analyzing the operations of existing hardware, software, and networking devices to predict the timing of upgrades, justify the cost of replacing and upgrading devices, and assist in troubleshooting. Performance monitoring ultimately reduces TCO and is a vital part of managing any IT environment. Performance monitoring helps answer important questions about your current environment. For example, you may want to know which activity specifically uses the most resources in your environment. If you determine that it is loading Web pages, then upgrading the RAM or the CPU speed of client machines may not help much.
    [Show full text]
  • An Evolutionary Study of Linux Memory Management for Fun and Profit Jian Huang, Moinuddin K
    An Evolutionary Study of Linux Memory Management for Fun and Profit Jian Huang, Moinuddin K. Qureshi, and Karsten Schwan, Georgia Institute of Technology https://www.usenix.org/conference/atc16/technical-sessions/presentation/huang This paper is included in the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16). June 22–24, 2016 • Denver, CO, USA 978-1-931971-30-0 Open access to the Proceedings of the 2016 USENIX Annual Technical Conference (USENIX ATC ’16) is sponsored by USENIX. An Evolutionary Study of inu emory anagement for Fun and rofit Jian Huang, Moinuddin K. ureshi, Karsten Schwan Georgia Institute of Technology Astract the patches committed over the last five years from 2009 to 2015. The study covers 4587 patches across Linux We present a comprehensive and uantitative study on versions from 2.6.32.1 to 4.0-rc4. We manually label the development of the Linux memory manager. The each patch after carefully checking the patch, its descrip- study examines 4587 committed patches over the last tions, and follow-up discussions posted by developers. five years (2009-2015) since Linux version 2.6.32. In- To further understand patch distribution over memory se- sights derived from this study concern the development mantics, we build a tool called MChecker to identify the process of the virtual memory system, including its patch changes to the key functions in mm. MChecker matches distribution and patterns, and techniues for memory op- the patches with the source code to track the hot func- timizations and semantics. Specifically, we find that tions that have been updated intensively.
    [Show full text]
  • 05 Vcloud Services Consultant
    Optimizing Windows for VMware View 4.5 Optimizing Windows for VMware View™ 4.5 (Optimizing Windows 7, Windows Vista and XP) Version 2.0 For use only by VMware PSO and VMware Solution Providers Consulting Service Delivery Aid – Not a Customer Deliverable Optimizing Windows for VMware View 4.5 Version History Date Ver. Author Description Rev iewers February 2011 V2.0 Tim Federwitz Second Release (Added Dav id Richardson, John Windows XP and Vista) Dodge, Matt Coppinger, Matt Wood August 2010 V1.0 Tim Federwitz First Release (Windows 7 John Dodge, Matt only ) Coppinger, Matt Lesak, Ry an Miersma, Justin Venezia © 2011 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. This product is covered by one or more patents listed at http://www.vmware.com/download/patents.html . VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc 3401 Hillview Ave Palo Alto, CA 94304 www.vmware.com © 2011 VMware, Inc. All rights reserved. Page 2 of 44 Optimizing Windows for VMware View 4.5 Contents 1. Introduction ......................................................................................... 4 1.1 Comparing Default and Optimized Windows 7 Installations ........................................ 4 1.2 How to use this Guide ............................................................................................... 4 2.
    [Show full text]
  • Comptia A+ Complete Study Guide A+ Essentials (220-601) Exam Objectives
    4830bperf.fm Page 1 Thursday, March 8, 2007 10:03 AM CompTIA A+ Complete Study Guide A+ Essentials (220-601) Exam Objectives OBJECTIVE CHAPTER Domain 1.0 Personal Computer Components 1.1 Identify the fundamental principles of using personal computers 1 1.2 Install, configure, optimize and upgrade personal computer components 2 1.3 Identify tools, diagnostic procedures and troubleshooting techniques for personal computer components 2 1.4 Perform preventative maintenance on personal computer components 2 Domain 2.0 Laptops and Portable Devices 2.1 Identify the fundamental principles of using laptops and portable devices 3 2.2 Install, configure, optimize and upgrade laptops and portable devices 3 2.3 Identify tools, basic diagnostic procedures and troubleshooting techniques for laptops and portable devices 3 2.4 Perform preventative maintenance on laptops and portable devices 3 Domain 3.0 Operating Systems 3.1 Identify the fundamentals of using operating systems 4 3.2 Install, configure, optimize and upgrade operating systems 5 3.3 Identify tools, diagnostic procedures and troubleshooting techniques for operating systems 6 3.4 Perform preventative maintenance on operating systems 6 Domain 4.0 Printers and Scanners 4.1 Identify the fundamental principles of using printers and scanners 7 4.2 Identify basic concepts of installing, configuring, optimizing and upgrading printers and scanners 7 4.3 Identify tools, basic diagnostic procedures and troubleshooting techniques for printers and scanners 7 Domain 5.0 Networks 5.1 Identify the fundamental
    [Show full text]
  • Windows Internals, Sixth Edition, Part 2
    spine = 1.2” Part 2 About the Authors Mark Russinovich is a Technical Fellow in ® the Windows Azure™ group at Microsoft. Windows Internals He is coauthor of Windows Sysinternals SIXTH EDITION Administrator’s Reference, co-creator of the Sysinternals tools available from Microsoft Windows ® The definitive guide—fully updated for Windows 7 TechNet, and coauthor of the Windows Internals and Windows Server 2008 R2 book series. Delve inside Windows architecture and internals—and see how core David A. Solomon is coauthor of the Windows Internals book series and has taught components work behind the scenes. Led by a team of internationally his Windows internals class to thousands of renowned internals experts, this classic guide has been fully updated Windows developers and IT professionals worldwide, SIXTH for Windows 7 and Windows Server® 2008 R2—and now presents its including Microsoft staff. He is a regular speaker 6EDITION coverage in two volumes. at Microsoft conferences, including TechNet As always, you get critical, insider perspectives on how Windows and PDC. operates. And through hands-on experiments, you’ll experience its Alex Ionescu is a chief software architect and internal behavior firsthand—knowledge you can apply to improve consultant expert in low-level system software, application design, debugging, system performance, and support. kernel development, security training, and Internals reverse engineering. He teaches Windows internals courses with David Solomon, and is ® In Part 2, you will: active in the security research community.
    [Show full text]
  • Building a Template for VDI in the 20'S
    Building a Template for VDI in the 20’s White Paper Introduction In this whitepaper, we will try and dispel some of the art involved in VDI and turn it back into a science. It’s all about the Template - the very heart of your VDI deployment. Whether you are focused on Healthcare, Manufacturing, Education, or any other industry, the IT used to power your business is often a "behind the scenes" resource that users do not directly interact with. For example, Active Directory just runs and there are numerous ways to make it redundant. Should a single server fail, the impact to the end-user is unnoticeable. VDI is the exception to this. If you get the Template wrong in VDI, the effect is immediately felt by the end- user. Choose the wrong amount of memory, and applications will perform poorly. Over optimize the desktop and it will be fast, but users won’t like to use the platform you are delivering – it could be as simple as they don’t have their desktop wallpaper. IT is now scrutinized by the most critical of judges, the end-user and the perception of the end-user community will make or break your VDI role out. There are loads of papers out there that tell you what to do. This paper will focus on the WHY. We have worked on countless VDI deployments and have seen templates done well and templates that can bring users screaming to your door. The WHY behind optimization will help you to create a Template that works for you organization.
    [Show full text]
  • User Resources
    A R R A K I S S Y S T E M S I N C D I G I L I N K * * * X T R E M E V e r s i o n 1 . 0 - 1 0 / 2 0 / 2 0 1 0 Quick Start Guide Congratulations on your purchase of the Digilink-Xtreme. This manual is intended to be a checklist for basic training. Please go through the entire manual and check-mark each [ ] in the sections as you go through it. Section 1: User Resources There are numerous resources that are available to the Digilink-Xtreme user. This section is to help familiarize the user with these resources. Instruction Manual One of the best resources is the instruction manual. This manual contains all necessary material for learning the software and hardware. You may find the latest version of the instruction manual by going to this link: http://www.arrakis- systems.com/ftp/pub/Automation/Documentation/Xtreme%20Manual.pdf [ ] check mark after reviewing the Xtreme Manual Video Tutorials Another exceptional resource is the Video Tutorials that are on our webpage. There are over 40 video tutorials that go through the basics of the software. These allow the user to train at their own pace and give visual style training for the software. These are available 24 hours a day, 7 days a week. You may find these Video Tutorials at this link: http://www.arrakis- systems.com/videotutorials.html [ ] check mark after reviewing the video tutorials webpage Application Notes There are often software revisions and updates that may be added to different features of the Digilink-Xtreme.
    [Show full text]
  • Unit 4: Memory Management
    Unit 4: Memory Management 4.2. Windows 2000 Memory Management Internals 1 AP 9/01 Windows 2000 Memory Management Internals Agenda: • Introduction • Process Memory • Free Memory • System Memory 2 AP 9/01 Windows 2000 Memory Manager • Provides 4 GB flat virtual address space (32-bit addresses) • Exports memory-mapped files • Allows pages shared between processes • Provides support for file system cache manager • Windows 2000 enhancements: – Integrated support for Terminal Server – Ability to use up to 64 GB physical memory – Performance and scalability improvements – Driver verifier 3 AP 9/01 4GB Virtual Address Space 00000000 Unique per process, .EXE code • 2 GB per-process accessible in Globals – Address space of one user or Per-thread user process is not directly mode stacks reachable from kernel mode other processes Process heaps .DLL code • 2 GB systemwide 7FFFFFFF – The operating system is 80000000 loaded here, and appears in Per process, Exec, Kernel, every process’s address accessible HAL, drivers, per- space only in thread kernel – There is no process for “the kernel mode mode stacks, operating system” (though there are processes that do C0000000 Win32K.Sys things for the OS, System wide, Process page tables, more or less in “background”) accessible hyperspace only in kernel File system cache mode Paged pool 4 FFFFFFFF Non-paged pool AP 9/01 3GB Process Space Option 00000000 Unique per process, • Only available on x86 accessible in Windows 2000 Advanced .EXE code user or kernel Server Globals mode – Boot with /3GB option Per-thread user in BOOT.INI mode stacks – Chief “loser” in system space is file system cache Per process, .DLL code Process heaps • Expands per-process address accessible space only in – But image must be kernel mode marked as “large address space aware” BFFFFFFF • 16GB maximum C0000000 Process page tables, physical memory System wide, hyperspace • A stopgap while we wait for accessible Exec, kernel, 64-bit Windows 2000 (Itanium) only in kernel HAL, mode5 FFFFFFFF drivers, etc.
    [Show full text]
  • Lesson 1: Using Task Manager Task Manager Provides Information About the Programs and Processes Running on Your Computer and the Performance of Your Computer
    19-2 Chapter 19 Monitoring and Optimizing System Performance Lesson 1: Using Task Manager Task Manager provides information about the programs and processes running on your computer and the performance of your computer. You can use Task Manager to start programs, to stop programs and processes, and to see a current view of your com- puter’s performance. After this lesson, you will be able to ■ Monitor programs by using Task Manager ■ Monitor processes by using Task Manager ■ Monitor system performance by using Task Manager ■ Monitor networking by using Task Manager Estimated lesson time: 25 minutes How to Monitor Programs Task Manager allows you to monitor applications and processes that are currently run- ning on your computer. It also provides information about the processes, including the memory usage of each one. It provides statistics about the memory and processor per- formance and network usage. You start Task Manager in any of the following ways: ■ Press CTRL+SHIFT+ESC ■ Right-click the Windows taskbar, and then click Task Manager ■ Press CTRL+ALT+DELETE Note Provided your computer running Windows XP Professional is in a domain environment, you can start Task Manager by pressing CTRL+ALT+DELETE. However, if your computer is in a workgroup environment, you might need to start Task Manager by selecting it, depending on how the logon and logoff options are configured. The Task Manager dialog box shown in Figure 19-1 has four tabs: Applications, Pro- cesses, Performance, and Networking. Lesson 1 Using Task Manager 19-3 F19us01 Figure 19-1 The Applications tab shows running applications and lets you terminate them.
    [Show full text]