• List Price: CDN$ 51.86
  • You Save: CDN$ 3.31 (6%)
Only 1 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
Intel+Threading+Building+... has been added to your Cart
+ CDN$ 6.49 shipping
Used: Good | Details
Sold by wobcanada
Condition: Used: Good
Comment: The book has been read but remains in clean condition. All pages are intact and the cover is intact. Some minor wear to the spine.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 3 images

Intel Threading Building Blocks: Outfitting C++ for Multi-core Processor Parallelism Paperback – Jul 12 2007

See all 2 formats and editions Hide other formats and editions
Amazon Price
New from Used from
Kindle Edition
"Please retry"
"Please retry"
CDN$ 48.55
CDN$ 29.93 CDN$ 1.37

Harry Potter and the Cursed Child
click to open popover

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Product Details

  • Paperback: 336 pages
  • Publisher: O'Reilly Media; 1 edition (July 22 2007)
  • Language: English
  • ISBN-10: 0596514808
  • ISBN-13: 978-0596514808
  • Product Dimensions: 17.8 x 1.8 x 23.3 cm
  • Shipping Weight: 481 g
  • Average Customer Review: Be the first to review this item
  • Amazon Bestsellers Rank: #508,021 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description

About the Author

James Reinders, Chief Evangelist of Intel Software Products, is a senior engineer who joined Intel Corporation in 1989 and has contributed to a number of projects, including the world's first TeraFLOP supercomputer (ASCI Red), compilers and architecture work for the iWarp, Pentium Pro, Pentium II, Itanium, and Pentium 4 processors. He has years of experience in processor architecture, optimizing compilers, parallel computer architecture, and making products for software developers.

Reinders is also the editorial columnist for the monthly "The Gauntlet" at www.devX.go-parallel.com, as well as the author of the Intel Press book titled "VTune Performance Analyzer Essentials" and contributor to the new book "Multi-Core Programming."

Customer Reviews

There are no customer reviews yet on Amazon.ca
5 star
4 star
3 star
2 star
1 star

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: HASH(0xa2738df8) out of 5 stars 6 reviews
107 of 108 people found the following review helpful
HASH(0xa26ece10) out of 5 stars Potentially useful technology, book could be better Aug. 25 2007
By J. S. Hardman - Published on Amazon.com
Format: Paperback
There are many views of how best to implement multi-threading and with multi-core processors now common the topic is becoming ever more relevant. Of course the best implementation method really depends on what you are trying to do. Are you implementing something that waits for a price update message from a derivatives exchange, parses the message, updates cached data, writes a log and forwards the message on to an algorithmic trading engine? If so, you'll probably be attracted to techniques different from someone calculating risk, bond prices etc. There is no one technique that suits every job.

Anyone working with multi-threading (and parallelism in general) keeps an eye on what techniques other people are using to see whether they may be useful. That's why I bought this book (Intel Threading Building Blocks) and TBB certainly looks like it will be of use for some multi-threaded applications that I develop, although not for all.

Starting with the most important question - have I learnt anything from reading this book. Yes, and I've learnt a couple of bits from reading the TBB source code too (downloadable from the web). Now for the detail...

Having read the book, am I now about to start using the Intel Threading Building Blocks library (downloadable from Intel)? The answer is yes, for some applications on some hardware architectures, but not for all of my multi-threaded applications. Importantly in terms of this book though, the first reason I looked at the TBB source code was to answer questions raised when reading the book, and that is my main issue with this book. For a developer who already has extensive multi-threading experience, this book raises quite a few questions that it doesn't answer.

Even some of the things that this book does answer are tucked away in the text a long way into the book. Here are three examples:
(1) The book tells you to create tasks, not explicitly work with threads. Where is the best description of a task? Page 267. It's not even in a glossary, but tucked away in the examples chapter. Somewhere in the first chapter would have been more useful.
(2) Personally, if I am told within the first few pages that TBB is based on the idea of developers implementing their systems as small tasks that are scheduled by the TBB scheduler I am immediately going to ask how that task is handled at a technical level. Ok, we're told quickly that it's written as a functor, and that functors may be executed on different cores, but does that mean that a thread is chosen from a thread pool to execute each functor, that (on Windows) fibers are used, that there is one manager thread running per core (with processor affinity set?) with each manager pulling tasks from its own queue, what are the performance implications of context switching and locking, etc? The author may think that the reader doesn't need this level of detail, but if somebody is going to the trouble of writing multithreaded code to improve performance I would think it very likely that they will want to know what is happening beneath the surface to ensure that they are using the best techniques. Some details of the scheduler are provided much further into the book (for instance we discover that last-in, first-out deques are used), but not enough and far too late.
(3) On page 133 there are two paragraphs discussing when task-based programming is inappropriate, a bit late in my opinion for those people for whom it does turn out to be inappropriate.

I also have issues with some of the things presented as absolute fact in the book. For example "Race conditions are less catastrophic than deadlocks". I disagree. With a deadlock your program stops, you know about it very quickly, you investigate and you sort it out. If it happens, it'll probably only happen once. With a race condition you may not even realise it exists, the application produces subtly incorrect results and hence your functionality goes awry. If that means your algorithmic trading engine decides to buy a million shares instead of doing nothing (or selling) then you are going to lose a lot of money very quickly. Possibly not just once, but day after day until you realise the race condition is there.

Then there are the bits that are just plain confusing. Here are two examples:
(a) We are told on page 271 that Task stealing is "Terrible" and "will disrupt cached data", but are told on page 283 that TBB is "unique because it rests on a few key decisions" including "Use task stealing". Hmmm...
(b) The code comment on page 231, "2 = 1 for SideShow and C". I know what it means, but adding a verb phrase would prevent the moment when the reader wonders just which proof is about to be presented that "2 = 1".

On the plus side, the book does discuss the split/join pattern, pipelines, atomic operations, benefits of working in user space, issues with the standard new operator (and hence libraries that make use of it), caching issues etc. There is also a chapter on general "Keys to Success" which is useful. There are also some reasonable examples towards the end of the book (although some half way through would be better replaced - demonstrating a point is one thing, but demonstrating it with realistic code is better).

Possibly outside the intended scope of the book, it might have been useful to briefly describe grid computing and whether Intel have plans to add a layer above TBB for use across grids instead of just on one machine, or whether Intel's plans for grid computing simply rely on a completely different model.

So to summarise, the TBB library from Intel looks like it could be very useful, this book will certainly get you started using it, but have no doubt that this book could have been better. Buy it if you will be using TBB, but until somebody writes a better book be prepared to read the TBB source code to find the answers to your deeper questions, or simply ask questions on Intel's web-site.
15 of 16 people found the following review helpful
HASH(0xa26ecde0) out of 5 stars Opens up your thinking about parallelism Jan. 27 2008
By rdf - Published on Amazon.com
Format: Paperback Verified Purchase
I agree with Hardman's review as far as it goes -- the book cannot go into as much detail as he would like since it is designed to be cross platform (and surprisingly also applicable to other similar chips e.g., AMD).

On the other hand, this book opens you up to an important area: how can you use a small number of cores to speed up your program, including those programs that appear serial at first (and maybe second) glance e.g., the cumulative sum of a vector.

The book has a lot of depth on the algorithms used and works through applications of differing complexity and varied domains.

As an extra bonus it provides annotated pointers to its intellectual predecessors, albeit not as extensive as Hillis' book.The Connection Machine (Artificial Intelligence)
3 of 3 people found the following review helpful
HASH(0xa250e0d8) out of 5 stars Complementary Manual of Intel's TBB documents April 3 2012
By Chunhyok Chong - Published on Amazon.com
Format: Paperback Verified Purchase
I think, this book is the complementary manual of Intel's TBB documents.
Because Intel provides some documents (tutorial, getting started, reference, design pattern) and example codes in the TBB package, but it could be somewhat difficult to find the sample code for all of TBB features like concurrent_*(queue, hash_map, vector) or TBB's task modules.

Although it proposes a good philosophy of concurrency but lacks concepts or diagrams to explain its codes parts.

A good example book.
1 of 1 people found the following review helpful
HASH(0xa26ecfb4) out of 5 stars more than just a book on TBB Oct. 24 2011
By Jeff - Published on Amazon.com
Format: Paperback Verified Purchase
While this book is about Intel TBB, I think it has some of the best introductory material on parallel programming in general. Chapter 2 is truly excellent in this respect.
HASH(0xa250e210) out of 5 stars Four Stars Nov. 26 2015
By t0rqued - Published on Amazon.com
Format: Kindle Edition Verified Purchase
Update it with the lambda expression variant!