Special

Introducing the “Welcome to Xojo” Bundle!

New to Xojo and looking for guidance? We've put together a terrific bundle to welcome you! Xojo Bundle

This bundle includes six back issues of the magazine -- all of year 21 in printed book and digital formats -- plus a one-year subscription (beginning with 22.1) so you'll be learning all about Xojo for the next year. It's the perfect way to get started programming with Xojo. And you save as much as $35 over the non-bundle price!

This offer is only available for a limited time as supplies are limited, so hurry today and order this special bundle before the offer goes away!

Article Preview


Buy Now

Issue 14.4 ('NSTableView')
Instant purchase and download via GumRoad!

FEATURE

Multiprocessing Part 4

More on Multicore processing

Issue: 14.4 (July/August 2016)
Author: Markus Winter
Author Bio: Markus is a Molecular Biologist who taught himself REALbasic programming in 2003 to let the computer deal with some exceedingly tedious lab tasks. Some call it lazy, he thinks it smart. He still thinks of himself as an advanced beginner at best.
Article Description: ion>No description availa
Article Length (in bytes): 9,267
Starting Page Number: be
Article Number: 14405
Related Link(s): None

Excerpt of article text...

As we've seen the last time, the environment variable already gives us the information about how many logical processing units are available to a given user. (Remember: how many you can use might be restricted by system policies, or perhaps the admin doesn't like you and has decided that four processing units are plenty enough for your unimportant tasks.) So why should we even bother with how many processing units the computer has?

Two reasons.

For one, you can bet that if your app says that you have "four cores available" when the user thinks they should have 72 available, that one or all of the following will happens:

  • the user thinks: "This app gives wrong information. Ditch it and use a better app."

  • a support call to admin ensues who will blame your software instead of taking responsibility

  • a rather irate bug report to you from a frustrated customer

...End of Excerpt. Please purchase the magazine to read the full article.