Skip to main content

High Throughput Computing week

We;ve just finished a week (well, four days) of talks, tutorials and discussion about High Throughput Computing. The event was opened by Miron Livny, leader of the Condor team, who gave an excellent introduction - the key point is that HTC is about the number of tasks that can be completed in a given time, whereas "traditional" High Performance Computing is about how much computing power can be brought to bear at a given time. As Miron puts it, Floating Operations per Year is not necessarily 60*60*24*7*52 Floating Operations per Second (FLOPS).

We've hosted events by the Condor team in the past, but for HTC week we extended our range. In particular, John Powers and Dan Ciruli of Digipede flew over from the Bay Area to tell us about their product. A day of hands-on tutorials allowed delegates to compare the strengths of Digipede and Condor, and the evening discussions included ways the systems could be used together.

Scheduled discussions looked at requirements for HTC in academia and in business, at Green IT, data handling and policy management. As one outcome of the discussions, we're looking to capture HTC design patterns, publish them on the web and incorporate them into training materials. On the academic side, we are planning to write a report to explain the policy issues to university heads of research computing.

There is talk of running this event again next year. We would like to extend the range of participants again, e.g. by looking to UnivaUD, DataSynapse or Platform. For more vendors to attend, we will need more commercial users, and vice versa, so we need to start encouraging people now. I'm wondering whether a small exhibition area might be useful to the commercial vendors and delegates - not a major trade show (with the concomitant expense) but enough to be an effective market place.

Watch this space - and get in touch if you're interested!

Comments

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-depth discussions abo

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community. Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham . Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterat