Friday, May 14, 2010

Exploding Processors in the Classroom

Has anyone noticed how a single core processor computer is becoming a rarity? Sure, netbooks are still single core, but I would be willing to wager they won’t remain like that too long. Two cores means that a single process will have a harder time monopolizing a computer. Yes, it can also benefit processor intensive performance, but the fact is beyond multimedia production and games there just is not much that taxes modern processors.

I recently received a mailing from AMD highlighting the release of the "Opteron 6000 Series Platform” featuring a 12-core processor. Now, I have seen enough advances in computing to know that statements like “640K ought to be enough for anybody” are quickly rendered moot. So the question I then considered was not whether this many cores would be useful in education, but how could we take advantage of this symmetry.

The first application that came to mind was combining this processing power with virtual machines. Again, everything old is new again, and “thin” computing once again seems attractive. A problem long held in engineering education environments is the need for students to have expensive specialized software but licenses agreements prohibiting broad distribution to students to use on their own computers. One approach to recognizing the ubiquity of personal computing (made even more affordable with the advent of netbooks) is to have virtual machines fully configured for engineering students accessed securely over campus intranets. These VMs would enable access to campus print and storage resources, and the expensive specialized software. The servers would provide adequate processing and memory so that even the lowliest of netbooks could be running Comsol Multiphysics or Aspen Plus with no more inconvenience than an occasional delayed screen refresh.

This has some significant cost benefits. Obviously, this can eliminate the need for fully equipped computer labs. Consider how many seats you normally target to serve with standalone machines in your labs at peak times. This is the number of processors you need available at most. The reality is, most software only needs significant processing resources in bursts, so a fraction of that many cores should be needed. If each lab machine runs $1500, and at least 12 of these can be replaced with a single server costing about $5000, that is about $13,000 savings in hardware. Don’t neglect the cost of electricity, and consider opportunities for additional savings in administration.

Much of the administration cost savings come through replication of disk images. Rather than pushing system images to many hard drives, some of which will fail during every cycle, you are working with a smaller library of mirrored disks, many of which can be automatically managed. There is also the opportunity to have discipline or course specific images so that the number of seats for certain types of license agreements can be reduced. And technologies like Windows 7 XP mode suggest that individual applications can be virtualized making student access even more cost efficient.

Naturally, there are are additional costs which may prevent this approach from being instantly feasible. Virtualization technology is still rather young and can be buggy. Your IT personnel and students will need to be trained in how to work with virtual machines, and students will need to be supported on accessing the resources from whatever computing device they use (could an iPhone or iPad be used here? or a Droid?). Network infrastructure, particularly wireless, is also a concern.

So is this a feasible option? I hope to hear from folks who have experimented with this approach, and I intend to conduct some experiments with this myself. It may be a step back from a cloud-based hosted application environment like Google Docs, but I don’t see Aspen Plus going that route anytime soon. But I am pretty sure no one will need more than 12 cores on a desktop PC anytime soon—soon being no more than at least 3 months from now!

No comments:

Post a Comment