Proceedings of Hotos IX: the 9Th Workshop on Hot Topics in Operating Systems

Total Page:16

File Type:pdf, Size:1020Kb

Proceedings of Hotos IX: the 9Th Workshop on Hot Topics in Operating Systems USENIX Association Proceedings of HotOS IX: The 9th Workshop on Hot Topics in Operating Systems Lihue, Hawaii, USA May 18–21, 2003 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2003 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Magpie: online modelling and performance-aware systems Paul Barham, Rebecca Isaacs, Richard Mortier, and Dushyanth Narayanan Microsoft Research Ltd., Cambridge, UK. Abstract A B Understanding the performance of distributed systems requires correlation of thousands of interactions be- Event Tracing Event Tracing tween numerous components — a task best left to a com- puter. Today’s systems provide voluminous traces from each component but do not synthesise the data into con- cise models of system performance. Models Models Performance We argue that online performance modelling should be Queries Query Engine a ubiquitous operating system service and outline sev- The diagram shows how requests move through different soft- eral uses including performance debugging, capacity ware components across multiple machines in a distributed sys- tem. Magpie synthesizes event traces from each machine into planning, system tuning and anomaly detection. We de- models that can be queried programatically. scribe the Magpie modelling service which collates de- tailed traces from multiple machines in an e-commerce Figure 1. Magpie architecture. site, extracts request-specific audit trails, and constructs probabilistic models of request behaviour. A feasibil- ity study evaluates the approach using an offline demon- operating system service. Performance traces should be strator. Results show that the approach is promising, but routinely collected by all machines at all times and used that there are many challenges to building a truly ubiq- to generate system performance models which are then uitious, online modelling infrastructure. made available for online programmatic query. To this end, we are building Magpie, an online modelling in- frastructure. Magpie is based on two key design princi- ples. Black-box instrumentation requires no source code 1 Introduction modification to the measured system. End-to-end trac- ing tracks not just aggregate statistics but each individual request’s path through the system. Computing today is critically dependent on distributed Fine-grained, low-overhead tracing already exists for infrastructure. E-mail, file access, and web browsing Linux [27] and Microsoft’s .Net Server [17]; the chal- require the interaction of many machines and software lenge is to efficiently process this wealth of tracing in- modules. When end-users of such systems experience formation for improved system reliability, manageabil- poor performance it can be extremely difficult to find ity and performance. Our goal is a system that collects the cause. Worse, problems are often intermittent or af- fine-grained traces from all software components; com- fect only a small subset of users and transactions — the bines these traces across multiple machines; attributes ‘it works for me’ syndrome. trace events and resource usage to the initiating request; Aggregate statistics are insufficient to diagnose such uses machine learning to build a probabilistic model problems: the system as a whole might perform quite of request behaviour; and compares individual requests well, yet individual users see poor performance. Ac- against this model to detect anomalies. Figure 1 shows curate diagnosis requires a detailed audit trail of each our envisioned high-level design. request and a model of normal request behaviour. Com- In Sections 2 and 3 we describe the many potential uses paring observed behaviour against the model allows of online monitoring and modelling. Section 4 describes identification of anomalous requests and malfunctioning the current Magpie prototype, which does online mon- system components. itoring but offline modelling. Sections 5 and 6 briefly We believe that providing such models should be a basic describe related work and summarize our position. USENIX Association HotOS IX: The 9th Workshop on Hot Topics in Operating Systems 85 2 Scenario: performance debugging tion 4 describes our first step towards these goals in the form of our offline modelling prototype. Joe Bloggs logs into his favourite online bookstore, Capacity planning. Performance prediction tools such monongahela.com,tobuy‘The Art of Surfing’ in prepa- as Indy [11] require workload models that include a ration for an upcoming conference. Frustratingly, he detailed breakdown of resource consumption for each cannot add this book to his shopping cart, though he transaction type. Manual creation of such models is time can access both the book details and his shopping cart. consuming and difficult; Magpie’s clustering algorithm His complaint to customer support is eventually picked (Section 4) automatically creates workload models from up by Sysadmin Sue. However, Sue is perfectly able to live system traces. order ‘The Art of Surfing’ from her machine, and finds Tracking workload level shifts. Workloads can change nothing suspicious in the system’s throughput or avail- qualitatively due to subtle changes in user behaviour ability statistics: she can neither replicate the bug nor or client software. For example, a new web interface identify the faulty component. might provide substring matching in addition to key- Consider the same website augmented with the Magpie word search. To reconfigure the system appropriately, online performance modelling infrastructure. Magpie we must distinguish level shifts from the usual fluctua- maintains detailed logs of resource usage and combines tions in workload. Magpie could do so by comparing them in real time to provide per-request audit trails. It models of current and past workloads. This might also knows the resource consumption of each request in each detect some types of denial-of-service attacks. of several stages — parsing, generation of dynamic con- Detecting component failure. Failure of software or tent, and database access — and can determine whether hardware components can degrade end-to-end perfor- and where Joe’s request is out of bounds with respect to mance in non-obvious ways. For example, a failed disk the model of a correctly behaving request. in a RAID array will slow down reads that miss in the Using Magpie’s modelling and visualization tools, Sue buffer cache. By tracking each request through each observes a cluster of similar requests which would not component, Magpie can pinpoint suspiciously behaving normally be present in the workload model. On closer components. examination, she sees that these requests spend a sus- Comparison-based diagnosis. Workload models could picious amount of time accessing the ‘Book Prices’ ta- be compared across site replicas to diagnose perfor- ble, causing a time-out in the front-end server. This is mance discrepancies. the problem which is affecting Joe and the culprit is a misconfigured SQL Server. Sue could not replicate the ‘Bayesian Watchdogs’. Given a probabilistic model of bug because her requests were redirected by an IP ad- normal request behaviour, we can maintain an estimate dress based load balancer to a different, correctly con- of the likelihood of any request as it moves through the figured replica. Within minutes the offending machine is system. Requests deemed unlikely can then be escorted reconfigured and restarted, and Joe can order his book into a safe sandboxed area. in good time for the conference. Monitoring SLAs. The emerging Web Services stan- This is just one performance debugging scenario, but dards [26] allow multiple sites to cooperate in servicing there are many others. File access, browsing and e-mail a single request. For example, an e-commerce site might in an Intranet may rely on Active Directory, authenti- access third-party services for authentication, payment, cation and DNS servers: slow response times could be and shipping. Magpie performance models could be caused by any combination of these components. Di- compared with service level agreements to check com- agnosing such problems today requires expert manual pliance. However, this does raise issues of trust and pri- ¡ ¢ £ ¤ ¥ ¦ £ ¡ § ¦ intervention using tools such as , and vacy of sensitive performance data. ¥ ¢ © § ¢ . Kernel performance debugging. Response times on a single machine are governed by complex interactions between hardware, device drivers, the I/O manager, the 3 Applications memory system and inter-process communication [14]. Event Tracing for Windows already traces all these OS components, enabling request tracking at this fine gran- Pervasive, online, end-to-end modelling has many uses ularity. apart from distributed performance debugging; here we list some of the most exciting ones. These applications End-to-end latency tuning. Scalable self-tuning sys- are research goals rather than accomplished facts. Sec- tems such as SEDA [25] optimise individual compo- 86 HotOS IX: The 9th Workshop on Hot Topics in Operating Systems USENIX Association points for this system. Active HTTP Web 20% 50% SQL Server Server Server Each instrumentation point generates a named
Recommended publications
  • A Programmer's Guide to C
    Download from Wow! eBook <www.wowebook.com> For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. Contents at a Glance Preface ����������������������������������������������������������������������������������������������������������������������� xxv About the Author ����������������������������������������������������������������������������������������������������� xxvii About the Technical Reviewer ����������������������������������������������������������������������������������� xxix Acknowledgments ����������������������������������������������������������������������������������������������������� xxxi Introduction ������������������������������������������������������������������������������������������������������������� xxxiii ■■Chapter 1: C# and the .NET Runtime and Libraries �����������������������������������������������������1 ■■Chapter 2: C# QuickStart and Developing in C# ����������������������������������������������������������3 ■■Chapter 3: Classes 101 ����������������������������������������������������������������������������������������������11 ■■Chapter 4: Base Classes and Inheritance ������������������������������������������������������������������19 ■■Chapter 5: Exception Handling ����������������������������������������������������������������������������������33 ■■Chapter 6: Member Accessibility and Overloading ���������������������������������������������������47 ■■Chapter 7: Other Class Details �����������������������������������������������������������������������������������57
    [Show full text]
  • Solid Code Ebook
    PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2009 by Donis Marshall and John Bruno All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Control Number: 2008940526 Printed and bound in the United States of America. 1 2 3 4 5 6 7 8 9 QWT 4 3 2 1 0 9 Distributed in Canada by H.B. Fenn and Company Ltd. A CIP catalogue record for this book is available from the British Library. Microsoft Press books are available through booksellers and distributors worldwide. For further infor mation about international editions, contact your local Microsoft Corporation office or contact Microsoft Press International directly at fax (425) 936-7329. Visit our Web site at www.microsoft.com/mspress. Send comments to [email protected]. Microsoft, Microsoft Press, Active Desktop, Active Directory, Internet Explorer, SQL Server, Win32, Windows, Windows NT, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of the Microsoft group of companies. Other product and company names mentioned herein may be the trademarks of their respective owners. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. This book expresses the author’s views and opinions. The information contained in this book is provided without any express, statutory, or implied warranties.
    [Show full text]
  • Adding Self-Healing Capabilities to the Common Language Runtime
    Adding Self-healing capabilities to the Common Language Runtime Rean Griffith Gail Kaiser Columbia University Columbia University [email protected] [email protected] Abstract systems can leverage to maintain high system availability is to perform repairs in a degraded mode of operation[23, 10]. Self-healing systems require that repair mechanisms are Conceptually, a self-managing system is composed of available to resolve problems that arise while the system ex- four (4) key capabilities [12]; Monitoring to collect data ecutes. Managed execution environments such as the Com- about its execution and operating environment, performing mon Language Runtime (CLR) and Java Virtual Machine Analysis over the data collected from monitoring, Planning (JVM) provide a number of application services (applica- an appropriate course of action and Executing the plan. tion isolation, security sandboxing, garbage collection and Each of the four functions participating in the Monitor- structured exception handling) which are geared primar- Analyze-Plan-Execute (MAPE) loop consumes and pro- ily at making managed applications more robust. How- duces knowledgewhich is integral to the correct functioning ever, none of these services directly enables applications of the system. Over its execution lifetime the system builds to perform repairs or consistency checks of their compo- and refines a knowledge-base of its behavior and environ- nents. From a design and implementation standpoint, the ment. Information in the knowledge-base could include preferred way to enable repair in a self-healing system is patterns of resource utilization and a “scorecard” tracking to use an externalized repair/adaptation architecture rather the success of applying specific repair actions to detected or than hardwiring adaptation logic inside the system where it predicted problems.
    [Show full text]
  • Visual Studio 2010 Tools for Sharepoint Development
    Visual Studio 2010 for SharePoint Open XML and Content Controls COLUMNS Toolbox Visual Studio 2010 Tools for User Interfaces, Podcasts, Object-Relational Mappings SharePoint Development and More Steve Fox page 44 Scott Mitchell page 9 CLR Inside Out Profi ling the .NET Garbage- Collected Heap Subramanian Ramaswamy & Vance Morrison page 13 Event Tracing Event Tracing for Windows Basic Instincts Collection and Array Initializers in Visual Basic 2010 Generating Documents from SharePoint Using Open XML Adrian Spotty Bowles page 20 Content Controls Data Points Eric White page 52 Data Validation with Silverlight 3 and the DataForm John Papa page 30 Cutting Edge Data Binding in ASP.NET AJAX 4.0 Dino Esposito page 36 Patterns in Practice Functional Programming Core Instrumentation Events in Windows 7, Part 2 for Everyday .NET Developers MSDN Magazine Dr. Insung Park & Alex Bendetov page 60 Jeremy Miller page 68 Service Station Building RESTful Clients THIS MONTH at msdn.microsoft.com/magazine: Jon Flanders page 76 CONTRACT-FIRST WEB SERVICES: Schema-Based Development Foundations with Windows Communication Foundation Routers in the Service Bus Christian Weyer & Buddihke de Silva Juval Lowy page 82 TEST RUN: Partial Anitrandom String Testing Concurrent Affairs James McCaffrey Four Ways to Use the Concurrency TEAM SYSTEM: Customizing Work Items Runtime in Your C++ Projects Rick Molloy page 90 OCTOBER Brian A. Randell USABILITY IN PRACTICE: Getting Inside Your Users’ Heads 2009 Charles B. Kreitzberg & Ambrose Little Vol 24 No 10 Vol OCTOBER 2009 VOL 24 NO 10 OCTOBER 2009 VOLUME 24 NUMBER 10 LUCINDA ROWLEY Director EDITORIAL: [email protected] HOWARD DIERKING Editor-in-Chief WEB SITE MICHAEL RICHTER Webmaster CONTRIBUTING EDITORS Don Box, Keith Brown, Dino Esposito, Juval Lowy, Dr.
    [Show full text]
  • CLR Profiling Apis Work Only for Managed Code
    Profiling Common Language Runtime Profiling This is preliminary documentation and subject to change Last updated: 2 July 2001 Page 2 Profiling Table of Contents 1 Profiling – Introduction ...........................................................................8 2 Goals for the Profiling APIs ......................................................................8 3 Non-goals for the Profiling APIs................................................................9 4 Profiling APIs – Overview ........................................................................9 5 Profiling APIs – Recurring Concepts ........................................................11 5.1 IDs................................................................................................11 5.2 Return Values .................................................................................12 5.3 Notification Thread ..........................................................................12 5.4 Nesting of Notifications ....................................................................12 5.5 GC-Safe Callouts.............................................................................13 5.6 How to profile a NT Service ..............................................................13 6 ICorProfilerCallback – Details.................................................................14 6.1 Runtime.........................................................................................14 6.1.1 Initialize....................................................................................14
    [Show full text]
  • A Hands-On Guide with Real-World Examples — Vaskaran Sarcar Foreword by Priya Shimanthoor
    Design Patterns in C# A Hands-on Guide with Real-World Examples — Vaskaran Sarcar Foreword by Priya Shimanthoor www.EBooksWorld.ir Design Patterns in C# A Hands-on Guide with Real-World Examples Vaskaran Sarcar Foreword by Priya Shimanthoor www.EBooksWorld.ir Design Patterns in C# Vaskaran Sarcar Whitefield, Bangalore, Karnataka, India ISBN-13 (pbk): 978-1-4842-3639-0 ISBN-13 (electronic): 978-1-4842-3640-6 https://doi.org/10.1007/978-1-4842-3640-6 Library of Congress Control Number: 2018946636 Copyright © 2018 by Vaskaran Sarcar This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the author nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made.
    [Show full text]
  • Smart Client Architecture and Design Guide
    Smart Client Architecture and Design Guide Foreword by Mark Boulter Smart Client Architecture and Design Guide patterns & practices David Hill, Microsoft Corporation Brenton Webster, Microsoft Corporation Edward A. Jezierski, Microsoft Corporation Srinath Vasireddy, Microsoft Corporation Mo Al-Sabt, Microsoft Corporation Blaine Wastell, Ascentium Corporation Jonathan Rasmusson, ThoughtWorks Paul Gale, ThoughtWorks Paul Slater, Wadeware LLC Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2004 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, BizTalk, InfoPath, MSDN, Outlook, Visual Basic, Visual C++, Visual C#, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Download File
    Columbia University Department of Computer Science Tech Report CUCS-015-05 Multi-Language Edit-and-Continue for the Masses Marc Eaddy Steven Feiner Department of Computer Science Columbia University New York, NY 10027 +1-212-939-7000 {eaddy,feiner}@cs.columbia.edu April 4, 2005 ABSTRACT We present an Edit-and-Continue implementation that allows regular source files to be treated like interactively updatable, compiled scripts, coupling the speed of compiled na- tive machine code, with the ability to make changes without restarting. Our implementa- tion is based on the Microsoft .NET Framework and allows applications written in any .NET language to be dynamically updatable. Our solution works with the standard ver- sion of the Microsoft Common Language Runtime, and does not require a custom com- piler or runtime. Because no application changes are needed, it is transparent to the appli- cation developer. The runtime overhead of our implementation is low enough to support updating real-time applications (e.g., interactive 3D graphics applications). Categories and Subject Descriptors D.3.3 [Software Engineering]: Programming Environments—Interactive environments; Testing and Debugging—Debugging aids; D.1 [Software]: Programming Techniques— Dynamic Software Updating; D.3.3 [Programming Languages]: Processors— Incremental compilers, dynamic compilers General Terms Experimentation, Languages, Performance Keywords dynamic software updating, online reconfiguration, patching, edit-and-continue, hot- swapping, rapid application development, .NET 1. INTRODUCTION Edit-and-Continue is a common debugging feature found in many integrated develop- ment environments (IDEs). It refers to the ability to pause an application, usually via a breakpoint, make changes to the source code that are recompiled in the background, and then continue execution with the modified application.
    [Show full text]
  • Session Title Session Sub Title (Optional)
    Pandurang Nayak Client Platform Evangelist Microsoft Corporation .NET Framework and Tools Roadmap 2006 .NET Framework 3.0 VS 2005 Extensions for .NET 3.0 (CTP) 2007 .NET Framework 3.5 Visual Studio 2008 Expression Blend 1.0 2008 .NET Framework 3.5 SP1 Visual Studio 2008 SP1 Expression Blend 2.0 .NET Framework Roadmap .NET Framework 3.5 SP1 WPF Enhancements Other Enhancements (ASP.NET, etc.) .NET Framework 3.5 WF & WCF WPF 3.5 LINQ Add-in Framework Enhancements .NET Framework 3.0 WPF WCF WF CardSpace .NET Framework 2.0 WinForms/ CLR Base Class Library ASP.NET WPF in a nutshell Rich Windows Applications Great Architecture + Great Graphics Rapid Prototyping 2D, 3D, Vector, Document Flow, Layouts, Composition, etc. WPF 3.5 Enhancements • .NET Framework • Interactive 2D on 3D • Cold Startup Client Profile • Pixel Shaders and Improvements • ~25MB client subset Effects Model • Several perf of .NET Framework • DirectX Interop enhancements • Customized install • New Controls • Profiling tools and experiences instrumentation Deployment Graphics Performance .NET Client Profile ~25MB Client-only Subset of .NET Fx Includes WinForms, WPF, LINQ, etc. Excludes ASP.NET, WCF, etc. 200KB fully customizable Bootstrapper .NET Framework Client Profile Using the Client Profile Deployment option in Visual Studio 2008 SP1 WPF 3.0 Graphics Recap Rich set of 2D drawing primitives Basic 3D functionality via Viewport3D Rich Media Integration Extensive Animation System Advanced Text Stack Bitmap Effects Imaging Compositor WPF 3.5 Graphics Enhancements True Interactive
    [Show full text]
  • Microsoft Mobile Development Handbook
    To learn more about this book, visit Microsoft Learning http://www.microsoft.com/MSPress/books/10294.aspx A05T623583.fm Page vii Tuesday, April 24, 2007 10:02 PM Table of Contents Foreword . xix Acknowledgments . xxi Introduction . xxiii Part I The Essentials of Mobile Application Development 1 .NET Compact Framework—a Platform on the Move. .3 Getting Started with Mobile Application Development in Visual Studio . 3 Choosing the Version of Visual Studio . 4 Other Development Software You Need . 5 Choosing Your Platform: Pocket PC, Smartphone, or Windows CE? . 7 The Difference Between Windows CE and Windows Mobile . 9 Choosing the .NET Compact Framework Version. 14 Understanding the Differences Between the .NET Framework 2.0 and .NET Compact Framework 2.0 . 20 Application Configuration Files. 23 ClickOnce . 24 Ngen.exe. 25 Remoting . 25 Serialization . 25 Printing . .25 Web Forms . 25 Understanding the Differences Between .NET Compact Framework Version 1.0 and Version 2.0 . 26 Windows Forms . 27 Display and Layout Management. 28 Data . .29 Communications . 30 What do you think of this book? We want to hear from you! Microsoft is interested in hearing your feedback so we can continually improve our books and learning resources for you. To participate in a brief online survey, please visit: www.microsoft.com/learning/booksurvey/ vii A05T623583.fm Page viii Tuesday, April 24, 2007 10:02 PM viii Table of Contents COM Interop . 30 Graphics Programming . 30 Security. 31 Threading . 31 Performance Monitoring . 31 Introducing .NET Compact Framework Version 3.5 . 31 Using Community Resources . 33 Microsoft patterns & practices Mobile Application Blocks. 34 OpenNETCF Smart Device Framework .
    [Show full text]
  • A Survey of Performance Analysis Tools
    A Survey of Performance Analysis Tools Patrick Wood, [email protected] Abstract In this paper, we present a survey of various tools that can be used to aid in performance analysis of computer software programs. We present and discuss different techniques in emerging performance analysis tools as well as provide examples of each type of method. For example, we will cover simple techniques such as timer routines with manual instrumentation to statistical profiling tools and more advanced dynamic instrumentation techniques, in which code can be monitored and changed on the fly. Additionally, a brief comparison of the tools will be presented with some tradeoff considerations. Keywords: Performance Analysis Tools, Profiler, Instrumentation, gprof, Pixie, CLR, ATOM, PIN, DynInst Table of Contents 1. Introduction 2. Brief History 3. Performance Analysis Objectives 4. Timers 5. Profiling Tools 5.1 gprof 5.2 SGI Pixie 5.3 CLR Profiler 5.4 Profiling Tools Summary 6. Instrumentation Methods 6.1 ATOM 6.2 PIN 6.3 DynInst 6.4 Instrumentation Methods Summary 7. Conclusion 8. Acronyms 9. References 1. Introduction Computer system and application performance is an essential and fundamental key in modern development. With increased complexity and requirements, applications are expected to perform greater computation in http://www.cse.wustl.edu/~jain/cse567-06/ftp/perf_tools/index.html 1 of 17 less time. Because of this increase in complexity, developers must turn to tools to aid in determining application or system bottlenecks. When using a performance tool, the workload under study is a real world application. Because of the real world workload under study, program tradeoffs in algorithm selection, data structure usage, and more can be evaluated through several runs of a tool.
    [Show full text]
  • Dynamic Analysis and Profiling of Multi-Threaded Systems
    Dynamic Analysis and Profiling of Multi-threaded Systems Daniel G. Waddington Nilabja Roy and Lockheed Martin Douglas C. Schmidt Advanced Technology Laboratories, Vanderbilt University, Cherry Hill, NJ, USA Nashville, TN, USA [email protected] {nilabjar, schmidt}@dre.vanderbilt.edu 1 Introduction A thread is a logical flow of execution within a program. In implementation terms, a thread is a lightweight representation of execution state, such as a program counter and associated registers, a runtime stack of activa- tion records, a priority, and scheduling state. Threads typically reside within a single process, which represents a more coarse-grained unit of protection and resource allocation. Threads have traditionally been used on single processor systems to help programmers implement logically concurrent tasks and manage multiple activities within the same program (Rinard, 2001). For example, a pro- gram that handles both GUI events and performs network I/O could be implemented with two separate threads that run within the same process. Here the use of threads avoids the need to “poll” for GUI and packet I/O events, as well as also avoids the need to adjust priorities and preempt running tasks, which is instead performed by the operating system’s scheduler. With the recent advent of multi-core and symmetric multi-processor (SMP) systems, threads represent logically concurrent program functions that can be mapped to physically parallel processing hardware. For example, a program deployed on a four-way multi-core processor must provide at least four independent tasks to fully ex- ploit the available resources (of course it may not get a chance to use all of the processing cores if they are oc- cupied by higher priority tasks).
    [Show full text]