DJ Thr3d'z Parizzelism Slam

It's back. The Intel Threading Challenge 2011 contest is gearing up for launch on Monday, 18 APR.

As was done last year, there are two divisions in which to compete: Apprentice and Master. Pick the level you think will challenge you the most and start solving the coding problems. The contest will have two phases: one now and one later in the year. Each phase will pose three problems in each division and contestants will have three weeks to solve each one to the best of their ability.

I can hear some of you yawning out there and saying, "Ho hum, another programming contest for another laptop or tablet or MP3 player or some other computing device." Not so! This year's prizes have been bumped up. Check out the prizes available for finishing in the top 3 for each problem at the contest prize page.

And did you see the Grand Prize? This is a "Wheel of Fortune" level prize: a trip to San Francisco to attend the Intel Developer Forum (IDF) in September! One trip for the winner of the Apprentice level and one for the Master level. And that's just for the first of two phases for this year's contest. Who knows what the big overall prize will be for Phase 2?

Contestants will again have the option of developing and testing their applications on the Intel® Manycore Testing Lab (MTL) platforms. There have been some changes in the MTL configurations that past contestants have not seen, yet. These changes aren't known to too many folks outside the MTL team, either, so Threading Challenge programmers will be some of the first to take advantage of them.

Click over to the contest's Official Rules page to get all the details about how enter and request an MTL account, the problem submission schedule, how solutions will be judged in each division and all the other nitty girtty details for participating in this year's Threading Challenge contest.

Why are you still reading this? Hurry! Go now! because the first problems are going to drop on 18 APR.

Good luck and good coding to everyone!
For more complete information about compiler optimizations, see our Optimization Notice.