Feeds

Team Utah grabs Mini Iron crown at little cluster compo

'Didya Hear the One About the Traveling Salesman?'

Internet Security Threat Report 2014

SC12 Until this year, the annual SC Student Cluster Competition focused entirely on seeing how much work teams of university students could wring out of 26 amps of juice. They can use any hardware/software combination that will run the required apps; the only limitation is that their configuration has to be shipping by the time of the show. (For an overview, click here.)

At SC12, organisers introduced a new cluster competition that ran alongside the traditional ‘Big Iron’ battle. This new ‘Mini Iron’ track provides student teams with identical LittleFe six-node Atom-based "clusters in a box". Three university teams and a team from a local Salt Lake City high school were challenged to find the best solution to the Travelling Salesman Problem.

Team Utah (representing hometown University of Utah) ended up winning the LittleFe competition, so congratulations to the Running Utes. (Or is it “Runnin’ Utes?”) They also prepared a couple of posters that explain the challenges they faced in the competition. The first poster (below) does a great job of laying out the Traveling Salesman problem and their initial approach to solving it. I use the word ‘initial’ because it wasn’t the solution they ended up using for the whole competition.

Team Utah's poster (click to enlarge)

They had a sort of hybrid strategy. First they split up the problem and sent each half to a separate node. The problem is evaluated at the node level, and if it’s still too complex (too many solutions to evaluate), then it is split again. Once the problem is small enough to fit within the processing envelope of the system, they use Concorde algorithms to do a near-exact solve on each branch. While this worked well in their testing runs, it wasn’t providing solutions quickly enough to keep Utah from falling behind their competitors at the show.

So at around 1.00 Mountain Time, they shifted gears and dumped the Concorde in favor of a group of other algorithms that performed much better. From that point on, Team Utah tended to run ahead of the other teams on succeeding data sets, piling up enough points to win the inaugural LittleFe Cup.

Their second poster shows what LittleFe actually looks like and some of the issues they ran up against when using it in the competition. This poster was designed back when the LittleFe competitors were going to be running the same apps as the Big Iron competitors. As the team alludes to in their graphic, running hard core scientific applications on this system is a bit problematic, and probably too ambitious for this first instance of the competition. LittleFe organisers changed over to the Travelling Salesman problem a few weeks before SC12, giving the teams a decent chance to prepare for the task.

Second poster (click to enlarge)

I was a bit surprised by the cooling issues. Sure, these systems were running flat-out, but damn, they’re only Atoms running at barely 1 GHz. Plus most of the teams were running them without skins, which gave them much better airflow. On top of that? They were tucked into one of the colder areas of the convention hall with an ambient temperature of maybe 68°F on the high side. Most of the LittleFe teams added additional fans to cool their boxlets, which seemed to do the trick.

While Team Utah took the overall LittleFe crown, the other teams were recognized for their achievements. CUNY Staten Island took second place (and it was pretty close throughout the competition). Slippery Rock University topped the judges’ interview portion of the competition. Team Skyline, the first and only high school team, garnered an honorable mention when they came out of nowhere to grab the lead; their homegrown algorithm dominated the college teams on the last data set of the competition. But that’s another story for another blog.

Congratulations to all of the LittleFe competitors. I’m looking forward to the next edition of the "Mini Iron" competition at SC13 in Denver. ®

Beginner's guide to SSL certificates

More from The Register

next story
NSA SOURCE CODE LEAK: Information slurp tools to appear online
Now you can run your own intelligence agency
Azure TITSUP caused by INFINITE LOOP
Fat fingered geo-block kept Aussies in the dark
Yahoo! blames! MONSTER! email! OUTAGE! on! CUT! CABLE! bungle!
Weekend woe for BT as telco struggles to restore service
Cloud unicorns are extinct so DiData cloud mess was YOUR fault
Applications need to be built to handle TITSUP incidents
Stop the IoT revolution! We need to figure out packet sizes first
Researchers test 802.15.4 and find we know nuh-think! about large scale sensor network ops
Turnbull should spare us all airline-magazine-grade cloud hype
Box-hugger is not a dirty word, Minister. Box-huggers make the cloud WORK
SanDisk vows: We'll have a 16TB SSD WHOPPER by 2016
Flash WORM has a serious use for archived photos and videos
Astro-boffins start opening universe simulation data
Got a supercomputer? Want to simulate a universe? Here you go
Microsoft adds video offering to Office 365. Oh NOES, you'll need Adobe Flash
Lovely presentations... but not on your Flash-hating mobe
prev story

Whitepapers

10 ways wire data helps conquer IT complexity
IT teams can automatically detect problems across the IT environment, spot data theft, select unique pieces of transaction payloads to send to a data source, and more.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
10 threats to successful enterprise endpoint backup
10 threats to a successful backup including issues with BYOD, slow backups and ineffective security.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Website security in corporate America
Find out how you rank among other IT managers testing your website's vulnerabilities.