MainComputersProgrammingThreads › Understanding Parallel Performance

Understanding Parallel Performance

Edit Page
Report
Scan day: 02 February 2014 UTC
52
Virus safety - good
Description: Explains how to accurately analyze the real performance of parallel code and lists some basic considerations and common costs.
Understanding Parallel Performance | Dr Dobb's Understanding Parallel Performance Understanding parallel performance. How do you know when good is good enough? Let's say that we've slickly written our code to apply divide-and-conquer algorithms and concurrent data structures and parallel traversals and all our other cool tricks that make our code wonderfully scalable in theory. Question: How do we know how well we've actually succeeded? Do we really know, or did we just try a couple of tests on a quad-core that looked reasonable and call it good? What key factors must we measure to understand our code's performance, and answer not only whether our code scales, but quantify how well under different circumstances and workloads? What costs of concurrency do we have to take into account?
Size: 819 chars

Contact Information

Phone&Fax:
Address:
Extended:

WEBSITE Info

Page title:Understanding Parallel Performance | Dr Dobb's
Keywords:
Description:Understanding parallel performance. How do you know when good is good enough?
IP-address:192.155.48.108

WHOIS Info

NS
Name Server: NS1.UBM-US.NET
Name Server: NS2.UBM-US.NET
Name Server: NS3.UBM-US.NET
WHOIS
Status: clientTransferProhibited
Date
Creation Date: 25-jun-1998
Expiration Date: 24-jun-2014