Software developers can't get to grips with multicore chips

Software developers are ill-prepared for the world of multicore processors. That's according to Herb Sutter, a software architect with Microsoft, speaking at the In-Stat/MDR Processor Forum.

"The free lunch is over," Sutter said. For a long time now, PC software performance has improved as PC processors from Intel and AMD ran faster and faster. Developers could simply make minor changes to existing software programs and watch their performance increase as the hardware engineers figured out ways to improve processor performance, he said.

The software development community recognizes that processor makers have been forced into multicore designs in order to deal with the heat problems caused by fast chips, but the community isn't sure that hardware designers understand just how much work they've created for the software industry, he said.

But multicore designs are forcing the client software world to deal with concurrency, the ability to break a single task into multiple parts that can be processed separately and reassembled later, Sutter said.

Developers who have been creating applications for servers have already cleared this hurdle, since multicore processors and multiple-processor systems have been common in the server market for several years, Sutter said. Many of these applications have been designed with multiple software threads that can take advantage of the parallelism of these systems, he said. Client application developers, however, have been stuck in a single-threaded world creating what Sutter called "sequential applications" for many years.

As a result, software developers need to come up with new ways of creating software, Sutter said. Just as the rise of object-oriented programming added a layer of complexity to assembly languages, concurrent programming likewise requires a new level of abstraction.

Microsoft is working on this problem through the Concur Project, an internal development group headed by Sutter that is trying to define those abstractions and tie them to hardware to "re-enable the free lunch," he said. But all software developers need to recognize that going forward, PC software needs to be developed with concurrency in mind, he said.