United States-English

Mostly Color

Performance update

Published 26 March 2008, 05:13 PM

A year ago I posted two entries on hyperthreads and multicores that were relatively popular. A short post on the the Performance Agora has an interesting comparison of the performance of the latest crop of Intel chips suggesting that the 8-way Penryn TPC-C performance now matches a 16-way Xeon of 2 years ago.

Performance experts like Neil Gunther worry mostly about database transactions and servicing HTTPS requests. For us color scientists working on color reproduction systems, the performance picture is different. Historically, we have always been fighting with the problem that we are ten years behind marking engine designers in terms of ripping pages as fast as the printers can consume them.

For us the hour of truth will come at the end of this year, when Intel will start shipping Nehalem. We will have to revisit our software architectures to take advantage of the new QuickPath platform architecture with fast integrated memory controllers. With QuickPath each processor has its own dedicated memory, so we will have to redesign how we map rendering in memory.

Faster bus and better stall prevention, will probably allow us to use more GPUs per system, which will likely require we rearchitect our whole rendering pipelines.

For more details on Nehalem, see Intel's whitepaper. For more details on QuickPath, see this other withepaper.

Technorati tags: , ,
Social bookmarking: DiggDigg del.icio.usdel.icio.us NowPublicNowPublic redditreddit NewsvineNewsvine GoogleGoogle



Comments

No Comments

Leave a Comment

(required)  
(optional)
(required)  


Type the digits above:
Information disclosed in this community becomes public. Exercise caution when deciding to disclose your personal information. HP reserves the right, but is not obligated to, edit or remove your comment if it contains personally identifiable information or other content HP deems unacceptable.  Opinions expressed are your personal opinions or those of the original authors, and not of HP. Please see HP's web Terms of Use for more details.